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:
Add metadata to a test that the test runner can then discover while running the tests (e.g. an attribute or annotation)
Define a test name/task id mapping (e.g. in the exercise's .meta/config.json file)
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_idfield, which is an integer that matches the number of the task as defined in the exercise'sinstructions.mdfile (note: the instructions start at index 1).This is an example of a test in the
results.jsonfile:You are completely free in how to implement this. Some options are:
.meta/config.jsonfile)Let me know if there are any questions.