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

Any reason why we aren't given the test suite to run locally? #100

Open
Norbo11 opened this issue Feb 11, 2019 · 1 comment
Open

Any reason why we aren't given the test suite to run locally? #100

Norbo11 opened this issue Feb 11, 2019 · 1 comment

Comments

@Norbo11
Copy link

Norbo11 commented Feb 11, 2019 •
edited
Loading

It would be very useful to just include the test suite used for assessment, instead of having to wait for the autotest to be triggered. Is there any reason why this isn't being done already?

If some of the tests give away clues as to how the implementation should look, maybe we can have a subset of a tests which don't reveal anything (such as the profiling tests)?
@jjd06
Copy link
Contributor

jjd06 commented Feb 12, 2019

For this CW you could have easily replicated the testing done based on the information in the log files I've been pushing. Aside from the benefit (to me) of not having to prepare/support the test scripts for you to use, I'm also weening you off relying on them. From CW5 you'll be on your own....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Norbo11 @jjd06