Upgrade to version 3 spec

[ErikSchierboom]

If possible, this test runner should be updated to version 3 of the test runner interface specification. In version 3, one additional feature is enabled: the ability to link individual tests to tasks. This allows the website to show which tests belong to which tasks.

The way tests are linked to tasks is via an (optional) task_id field, which is an integer that matches the number of the task as defined in the exercise's instructions.md file (note: the instructions start at index 1).

This is an example of a test in the results.json file:

{
  "name": "Expected oven time in minutes",
  "status": "pass",
  "task_id": 1,
  "test_code": "Assert.Equal(40, Lasagna.ExpectedMinutesInOven());"
}

You are completely free in how to implement this. Some options are:

1. Add metadata to a test that the test runner can then discover while running the tests (e.g. an attribute or annotation)
2. Define a test name/task id mapping (e.g. in the exercise's .meta/config.json file)
3. Any other option you can think of...

Let me know if there are any questions.

[wolf99]

Hi @ErikSchierboom ,

The C track does not yet have any concept exercises. As such I am not sure how we should reason about how tasks can be defined, meaning we cannot reason about how tasks should be mapped.

I am concerned that where I to implement something here in anticipation of future addition of concept exercises then the requirement will be forgotten on the language track by then.

Suggestions on how to proceed?

[ErikSchierboom]

@wolf99 As the C track does not have any Concept Exercises, you can ignore this issue. How you do that is up to you: closing, adding something to the title, whatever works for you.