Upgrade to version 2 spec
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Read the linked version 2 test runner interface specification first, then inspect how this runner currently produces results.json. Implement the detailed per-test information required by the specification, including status, failure message, and test code, and verify that the generated results.json matches the version 2 format.
Written by the indexing model from the issue text.
Description
If possible, this test runner should be updated to version 2 of the test runner interface specification.
The version 2 spec differs from version 1 in that the results.json file contains detailed information on individual tests.
This information includes things like:
- The test status (passing/failing)
- The error message (if failing)
- The test code that was used to run the test
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.
- Dominant language
- Shell
- Stars
- 2
- Forks
- 6
- Avg merge
- 7m
- Merged PRs (30d)
- 1
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from exercism/vimscript-test-runner
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
exercism/vimscript-test-runner#27 · 4 comments ·
-
x:action/improve x:knowledge/advanced x:module/test-runner x:size/large x:type/coding
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in exercism/vimscript-test-runner
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
alunduil/alunduil-infrastructure#629 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
duckdb/duckdb-skills#19 ·