Upgrade to version 2 spec

[ErikSchierboom]

We've recently updated the test runner interface specification to allow for two types of test runners, identified via a new version property in the results.json file (see the spec for the version property):

1. version: 1 test runners are quite basic, and only detect if either all tests passed or not. These test runners capture the console output of the test runner and output that. They do not include details on individual tests passing/failing
2. version: 2 test runners contain detailed information on individual tests passing/failing. We've recently added a required field named test_code, which contains the code the test ran to verify the behavior (see the spec for the test_code property).

The test runner's output is currently what I refer to as version 1.5: it contains the individual test information, but does not yet contain the test_code key. If possible, the test runner should be updated to also include the test code, in which case the version property should also be added with 2 as its value.

You are completely free on how you want to extract the test code, either via the AST or via finding the test code in the source code text via string manipulation.

Let me know if there are any questions.

[senekor]

I think this has to be done with AST parsing. Some test files use modules to organize the tests, I believe there is even one exercise where test cases are generated with a declarative macro.

The spec also says something about returning test results in the same order as the tests are defined. I believe this is currently not done correctly. Having AST information about the test file would be the perfect preparation to fix that as well.