-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
Update each tracks tests.toml file #370
Labels
Comments
kytrinyx
added a commit
that referenced
this issue
Nov 14, 2022
This removes an entry for an unimplemented test. See #370
kytrinyx
added a commit
that referenced
this issue
Nov 14, 2022
This removes several entries for unimplemented tests. See #370
kytrinyx
added a commit
that referenced
this issue
Nov 15, 2022
* Rectify tests.toml for roman-numerals This removes an entry for an unimplemented test. See #370 * Normalize test descriptions in roman-numerals This uses the descriptions found in the canonical-data in problem-specifications for the test descriptions in the roman-numerals test suite. * Sync roman-numerals with problem-specifications This brings in updates to the instructions and metadata, as well as adding several new tests.
kytrinyx
added a commit
that referenced
this issue
Nov 15, 2022
* Rectify tests.toml for raindrops This removes several entries for unimplemented tests. See #370 * Delete extraneous test from raindrops The 'big prime' test does not exist in the canonical-data for this exercise. * Normalize test descriptions in raindrops This updates the raindrops tests to use the same test descriptions as the canonical-data in problem-specifications. * Sync raindrops with problem-specifications This brings in updates to the instructions, normalizes the exercise's config.json, and adds several new tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #362 a tests.toml file was added to each track in order to track the list of implemented tests for that exercise. By default every test was listed as existing, which I doubt is the reality. We need to go through each test to match the implementation here with the problem specifications repo.
More details in #362
The text was updated successfully, but these errors were encountered: