Added custom pytest markers to Python tester to record MarkUs metadata #592
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.
This pull requests updates the Python tester to add four new
pytestcustom markers:markus_tag(for adding tags to a submission)markus_annotation(for adding annotations to a submission)markus_overall_comment(for adding overall comments to a submission)markus_message(for displaying messages in the test output)The first two build on #582 and MarkUsProject/Markus#7387. The third takes advantage of existing autotester functionality (which is currently only used by the PyTA tester).
The fourth modifies the current Python tester behaviour: currently, the only test output shown to students is error messages. The new marker allows the instructor to provide custom messages that are displayed to student regardless of test status; these can be used to provide feedback even when a test passes, or to provide additional information when a test fails.