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.

This is the bash list-ops exercise:

Add output information to results.json, as per: exercism/automated-tests#34

Instead of building those filenames in run.sh, simply extract them from the exercise's config.

This will remove the need to first check if the test file is *.bats and if not using *_test.sh.

This will future-proof us if we want to change the solution from *.sh to *.bash or remove the extension entirely.

What are the new and interesting features introduces since v1.5 (as hardcoded in the Dockerfile)

1. capture debugging stdout
2. associate the test body with the tests run.

I was encountering issues when running bats on my Git bash on Windows. When I read through some conversation online and figured out they have migrated to Bats Core.

It works well for me and the testing results looks exactly the same with Bats. Should we update the Readme and suggest to use Bats-core instead?

I'm new to open source but I wish to contribute to the community too. Not sure if it's appropriate posting this as a issue.

Relates to #17

The symptoms of commands used in user solutions that are missing from the test-runner docker OS: "status 2"

In line with our new org-wide policy, the master branch of this repo will be renamed to main. All open PRs will be automatically repointed.

GitHub will show you a notification about this when you look at this repo after renaming:

In case it doesn't, this is the command it suggests:

git branch -m master main
git fetch origin
git branch -u origin/main main

You may like to update the primary branch on your forks too, which you can do under Settings->Branches and clicking the pencil icon on the right-hand-side under Default Branch:

We will post a comment below when this is done. We expect it to happen within the next 12 hours.

Given:

Tidy up the output by excluding the "skip" lines.