Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The path to ouput of Runners should not be hard coded #47

Open
danglotb opened this issue Sep 11, 2018 · 0 comments
Open

The path to ouput of Runners should not be hard coded #47

danglotb opened this issue Sep 11, 2018 · 0 comments
Labels
enhancement First Issue First issue are easy to handle. Beginners can take care of it. task available

Comments

@danglotb
Copy link
Member

For now, the loader is looking into target/dspot/<name>.ser or appending the configuration workspace.

However, it would be great to be able to use a custom path, to use the testrunner outside of DSpot.

Thus, with #46 we could read the result from the outside.
@danglotb danglotb added enhancement task available First Issue First issue are easy to handle. Beginners can take care of it. labels Sep 11, 2018
@danglotb danglotb changed the title The path to ouput of Runners should not be valued The path to ouput of Runners should not be hard coded Sep 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement First Issue First issue are easy to handle. Beginners can take care of it. task available
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danglotb