general overview

This is the next (and last) big thing to do before getting the track released. Time to get serious with it.

In this issue, I summarize my understanding of the guidelines, to make sure I understand what I have to do and try to sketch a concrete action plan.

Overall, I think this should be easier than it looks, because we should have almost all pieces ready, namely
- we already have a bash script to test exercises
- we have a docker image we use in the CI.

I understand there are three levels of ambition:

- LEVEL 1: A single grade for the whole exercise, pass if everything is fine and fail otherwise
- LEVEL 2: info for individual tests of the exercise.
- LEVEL 3: let's think about this in the future, sometimes you gotta choose your battles

So the main challenge is to implement the logic to generate the JSON.

My rough roadmap:

- [x] implement level 1: this should be fairly straightforward, run `mason test` and use the resulting exit code to choose what to write in the JSON. Could be done as a small bash script
- [x] Make it work in docker.
- [ ] Implement level 2: there are a few approaches. For example, capture the output of `mason test --show` and parse it to get the result of each individual test. This can be done with a quick and dirty script. Alternative add a method to `Test` class that generates the JSON while running the tests, requires some work but probably not too much.

Comments? Suggestions?