Open pdawyndt opened 2 months ago
I guess we just forgot to clean the stack trace of the main call, because what happens above is as expected (test plan first executed main call and then calls a function, but the main call throws an exception that is displayed by the Python runtime on stderr, and exits, probably with a non-zero exit status that is not shown here). So all we should do is hide the execution_0.puy lines in the stack trace.
This test suite should check if a call to the function
generate_division_by_zero
raises aZeroDivisionError
.However, if the following solution is submitted
The stack trace exposes some of the TESTed internals that should remain hidden for students: