Upgrade to version 3 spec
还没有人认领这个 Issue。
评估
调研方向
首先阅读链接的测试运行器接口规范，并查看此 Lua 测试运行器当前如何实现版本 1。检查练习说明 instructions.md 和 results.json 格式，并考虑 .meta/config.json 或测试元数据是否可以表示 task_id 值。完成的标准是支持版本 3 接口，使单个测试能够链接到编号任务。
由索引模型根据 Issue 内容生成。
描述
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.jsonfile) - Any other option you can think of...
As this test runner currently implements version 1 of the test runner specification, it might be good to first upgrade to version 2 of the test runner specification before upgrading to version 3.
Let me know if there are any questions.
- 主要语言
- Lua
- 星标
- 0
- 派生
- 7
- 平均合并
- 6 小时 18 分钟
- 30 天内合并 PR
- 2
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
pterodactyl/game-eggs#657 ·
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 65/100
stalker57241/tabview#10 ·
-
feature-request mini.icons
难度 1/5 1 小时以内 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 62/100
mfussenegger/nvim-dap#1613 · 2 条评论 ·
-
enhancement
难度 2/5 1-3 小时 新手友好度 68/100