A passing test is only evidence for the configuration it ran on

A passing test is only evidence for the configuration it ran on

以下是我用来解释为什么通过的测试需要背景信息时所使用的虚构发布评审案例。一块控制板在修订版 B 和固件 1.8 下通过了热测试。一周后,候选发布版本使用了修订版 C 和固件 1.9。你的仪表板上仍然显示“热测试:通过”。在将该通过结果沿用之前,请检查实际发生了什么变化,以及这些变化是否会影响测试。

Record three things separately: the configuration tested, the configuration intended for delivery, and the decision about whether the old evidence applies. The first two should be concrete enough for someone else to compare, for example board revision, firmware build, test setup, and the relevant operating limits. The third needs an owner and a reason.

分别记录三件事:已测试的配置、计划交付的配置,以及关于旧证据是否适用的决定。前两项应足够具体,以便他人进行比较,例如电路板修订版、固件版本、测试设置和相关的操作限制。第三项需要责任人和理由。

For each difference, write one decision: Reuse the evidence if the responsible engineer can explain why the change does not affect the test condition or result. Run a targeted check if a specific changed part or behavior affects the evidence. Rerun the test when the impact is uncertain and the old evidence cannot support the release decision.

针对每一项差异,写下一个决定:如果负责的工程师能够解释为什么该变化不会影响测试条件或结果,则复用该证据。如果某个特定的变更部件或行为会影响证据,则进行针对性检查。当影响不确定且旧证据无法支持发布决定时,重新运行测试。

In this example, a changed regulator could alter the board’s thermal behavior. That does not tell you which test to repeat by itself. It tells you to inspect the regulator’s operating conditions and ask the verification owner to decide what evidence the release needs. Until they decide, mark the release evidence as pending.

在此示例中,更换的稳压器可能会改变电路板的热性能。这本身并不能告诉你应该重复哪项测试。它要求你检查稳压器的工作条件,并要求验证负责人决定发布需要什么样的证据。在他们做出决定之前,请将发布证据标记为“待定”。

Try this in your next release review: pick one result labeled pass and ask someone to show the tested build, the intended build, and the decision connecting them. If the team cannot reconstruct that decision from the record, the status needs more context. Tymeline published a free example worksheet with fields for this review: engineering program review kit Tymeline manages this publishing account.

在下一次发布评审中尝试这样做:挑选一个标记为“通过”的结果,并要求某人展示已测试的版本、计划交付的版本,以及连接两者的决定。如果团队无法从记录中重构该决定,则该状态需要更多的背景信息。Tymeline 发布了一个包含此评审字段的免费示例工作表:工程项目评审工具包,Tymeline 管理此发布账户。