Bug: No Output When Command Fails to Run Due to Mistake in --mark Argument

[hemanialaparthi]

When a student runs the following command:

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.

[gkapfham]

Hi @hemanialaparthi, thanks for raising this bug! This is an important problem to resolve and I agree that I have also faced this issue. Can you give an example of the output that you see when you think that this defect is triggered?

[boulais01]

@hemanialaparthi Would you mind providing examples of the issue vs. expected and if there's been any progress on this bug?

[boulais01]

Hello @hemanialaparthi, do you have any updates on this or examples?