generator: retain nested test case structure #1889
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The logic to extract the function names from the lib.rs stub to use it
for exercise generation doesn't really add any value, it just makes
things more complicated. First of all, the Rust code itself.
But also the tera templates, which contain a {{ fn_names[0] }}.
All for saving a few characters of typing when creating a new template.
That's not worth it in my opinion. The templating context should only
contain things that actually change dynamically, namely the test data.
ErikSchierboom
approved these changes
Apr 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the generator flattened any nesting of test cases from problem-specifications. This worked alright for medium-complexity exercises. However, it makes writing a functional test template harder in the general case. An example is the exercise
forth, which has test cases with the same description across different test groups. Flattening the groups leads to tests with the same name being generated. Preserving the structure makes it possible to organize the tests into one module per test group, solving the naming conflicts.The three commits contain:
additional-tests.jsonwere also necessary, such that the additional tests would have the same nesting structure as the standard ones.additional_tests_are_documented. It reads theadditional-tests.jsonfiles and therefore has to account for the new structure as well.