https://github.com/exercism/haxe-test-runner
https://github.com/exercism/haxe-test-runner
community-contributions-paused exercism-test-runner exercism-tooling
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/exercism/haxe-test-runner
- Owner: exercism
- License: mit
- Created: 2021-02-02T17:27:55.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2024-04-24T23:31:39.000Z (about 1 year ago)
- Last Synced: 2024-05-01T11:25:18.607Z (about 1 year ago)
- Topics: community-contributions-paused, exercism-test-runner, exercism-tooling
- Language: Haxe
- Size: 127 KB
- Stars: 2
- Watchers: 5
- Forks: 5
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# Exercism Haxe Test Runner
The Docker image to automatically run tests on Haxe solutions submitted to [Exercism].
## Running the Tests
To run all of the tests, do the following:
1. Open a terminal in the project's root
2. Run `bin/run-tests.sh`
These are [golden tests][golden] that compare the `results.json` generated by running the current state of the code against the "known good" `test//results.json`. All files created during the test run itself are discarded.
When you've made modifications to the code that will result in a new "golden" state, you'll need to generate and commit a new `test//results.json` file.
To run the tests of an arbitrary exercise, do the following:
1. Open a terminal in the project's root
2. Run `./bin/run.sh `
Once the test runner has finished, its results will be written to `/path/to/output/dir/results.json`.
## Run the test runner on an exercise with Docker
_This script is provided for testing purposes, as it mimics how test runners run in Exercism's production environment._
To run the tests of an arbitrary exercise using the Docker container, do the following:
1. Open a terminal in the project's root
2. Run `./bin/run-in-docker.sh <./relative/path/to/solution/dir/> <./relative/path/to/output/dir/>`
Once the test runner has finished, its results will be written to `./relative/path/to/output/dir/results.json`.
**Note**: the solution and output directory's **MUST** be relative paths!
[test-runners]: https://github.com/exercism/automated-tests/blob/master/docs/introduction.md
[golden]: https://ro-che.info/articles/2017-12-04-golden-tests
[exercism]: https://exercism.io