Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Preserve test run history

未关闭
  • 哪里不对？
#301 2 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@yunhsuan0510 已经在做这个了。

开始于 2026年10月14日。

  • #305 来自 @yunhsuan0510 —— 未关闭

评估

难度
3/5
预计耗时
1-2 天
新手友好度
62/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript
领域
frontend, testing

调研方向

Start in web/interview.js, where the Run tests handler and the Markdown export call reportMarkdown(), then read web/runners.js to see how each test result object is built, including where input is set only for custom or failed cases. Next, check web/render.js to see how the report is assembled. Done means each run is appended to a testHistory array, passing cases keep their input, and a Test Run History section appears in the exported Markdown, with regression tests under tests/browser/ covering it.

由索引模型根据 Issue 内容生成。

描述

Description

Currently, the interview report only preserves the candidate's final version of the code. Intermediate code changes, failed test runs, and error messages during the interview are not fully recorded.

This makes it difficult for candidates to review their mistakes after the interview, understand why their solutions failed, and reflect on how they could improve their problem-solving approach.

Expected Behavior

  • Record each test run when the candidate clicks Run tests.
  • Preserve the timestamp, test results, expected values, actual values, and available error messages for each run.
  • Include a code snapshot only when the code differs from the previous test run, avoiding unnecessary duplication.
  • Keep only the 10 most recent test runs to limit the size of the exported Markdown report.
  • Include the test run history in the final Markdown interview report, alongside the existing final code and interview transcript.
  • Preserve previous records within the retained history instead of overwriting them with the latest test results. Display the additional records only in the Markdown report without adding them to Past Attempts Reports.

Proposed Solution

1. Record test run history

Update web/interview.js to add a testHistory array to the interview state.

Before executing tests, capture the current code, programming language, and timestamp. After execution, append a record containing:

  • Run number and timestamp
  • Programming language
  • Code snapshot, if the code has changed since the previous run
  • Number of passed and total tests
  • Setup errors and individual test case results
  • Available input values, expected outputs, actual outputs, and error messages

After recording each run, retain only the 10 most recent entries.

2. Avoid duplicate code snapshots

Compare the current code with the code from the previous test run.

  • If the code has changed, save a new code snapshot.
  • If the code has not changed, record the test results without duplicating the code snapshot.

This reduces the size of the exported report while preserving meaningful code changes.

3. Include test history in the Markdown report

Update web/render.js to accept a testHistory parameter and generate a Test Run History section.

Each run should include its timestamp, test summary, available test case details, and a code snapshot when applicable.

Update the Markdown export function in web/interview.js to pass state.testHistory to reportMarkdown().

The existing final code section and interview transcript should remain unchanged.

4. Add regression tests

Update the relevant tests under tests/browser/.

Example Result
Image
主要语言
Rust
星标
160
派生
64
平均合并
1 天 10 小时
30 天内合并 PR
112

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

sysprog21/codetrial 的其他 Issue

查看 sysprog21/codetrial 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。