-
-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Build Test Runner #4
Comments
This was referenced Jan 29, 2021
@ErikSchierboom I'm playing around with making a crystal test-runner. :) |
@neenjaw Brilliant! Let me know if you need any help. |
Will do, it's going alright so far! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Exercism v3, one of the biggest changes is that we'll automatically check if a submitted solution passes all the tests.
We'll check this via a new, track-specific tool: the Test Runner. Each test runner is track-specific. When a new solution is submitted, we run the track's test runner, which outputs a JSON file that describes the test results.
The test runner must be able to run the tests suites of both Concept Exercises and Practice Exercises. Depending on the test runner implementation, this could mean having to update the Practice Exercises to the format expected by the test runner.
Each track must build a test runner according to the spec. For tracks building a test runner from scratch, we have a starting guide and a generic test runner that can be used as the base for the new test runner.
The text was updated successfully, but these errors were encountered: