Command testing by parsing

[gubogaer]

This branch introduces the contextWithParsing function. This context can be used to test intermediate (printed/returned) results that are not saved in an object. This can be done by splitting the student code using comments following a certain pattern. The context function will run the code section by section alternated by the test defined for this section.

[gubogaer]

Please style your code consistently with the rest of the project (space after for and if, space between ) and {, space around ==/!=).

• code style consistency should be fixed

I feel like this doesn't handle mismatches between the exercise's requested sections and the student's provided sections. AFAICT, there is no message when the studnt has superfluous sections, and same for missing? In those cases, a warning to the student also feels appropriate.

• superfluous section titles are threated the same as normal comments (skipped)
• missing sections were a problem, a student could avoid the testing for a section by removing the section titles. This should now be fixed. Removing a section title causes a parsing error

Also, IIUC this throws away any code that is not in a section, right? (So all code before the first section, I guess). A student might set up some results/variables there, which could make the rest of the code invalid, even though their solution has correct results when run locally. You could add a warning for that case, but I'd prefer if we executed all submitted code, but just didn't do any tests for a preamble.

• This was not the case all student code is being evaluated except when the there are no section titles and no testcases

[bmesuere]

@gubogaer It seems like some exercises are already using this? We're getting some internal errors. However, @chvp is ill and I'm abroad so we're unable to fix this today.

[gubogaer]

That's correct luckily I made alternative testing methods which i will be using for the upcoming practica today. But thanks for noticing!