poetry run execexam . tests/ --mark "question_one_part_a" --fancy
The test runs successfully, and the expected output is provided. However, if there is a mistake in the --mark argument, for example:
poetry run execexam . tests/ --mark "question_one_part_" --fancy
There is no output indicating whether the test failed to run due to an incorrect mark name or some other issue. As a result, students are left confused, unable to determine whether their test didn't run because of an error in their program or because of a mistake in the file name/mark argument.
Expected Behavior
There should be an explicit message or error output informing the user that the test didn't run due to an invalid --mark argument. This way, students will know to check the argument for mistakes, rather than assuming the issue lies in their code.
When a student runs the following command:
poetry run execexam . tests/ --mark "question_one_part_a" --fancyThe test runs successfully, and the expected output is provided. However, if there is a mistake in the --mark argument, for example:
poetry run execexam . tests/ --mark "question_one_part_" --fancyThere is no output indicating whether the test failed to run due to an incorrect mark name or some other issue. As a result, students are left confused, unable to determine whether their test didn't run because of an error in their program or because of a mistake in the file name/mark argument.
Expected Behavior
There should be an explicit message or error output informing the user that the test didn't run due to an invalid --mark argument. This way, students will know to check the argument for mistakes, rather than assuming the issue lies in their code.