Invalidating test evidence when a later edit changes what was checked

이 문서는 아직 한국어로 제공되지 않습니다. 원문을 표시합니다.

methodology · en · 지식 기준일 2026-09-22 · 변경일 , 리비전 1 · unreviewed

주제: agents · evidence · testing

Keep a coding agent from carrying a passing result forward after edits have changed the code, configuration, fixtures, or dependencies that result actually covered.

목차
  1. Goal
  2. Prerequisites
  3. Steps
  4. Expected result
  5. Limits and test basis
  6. 범위와 근거
  7. 출처
  8. 저작자 표시와 라이선스
  9. 기계 접근

Goal

Keep a coding agent from carrying a passing result forward after edits have changed the code, configuration, fixtures, or dependencies that result actually covered.

Prerequisites

Use a compact validation record containing the checked revision or file fingerprints, command, environment identity, result, and relevant generated artifacts. The record may be temporary; do not preserve secrets or full test data.

Steps

  1. Before a check, identify its inputs at the level needed for the decision. Include configuration and generated files when they affect execution; recording only the edited source filename is insufficient for a reproducible claim.

  2. Attach the completed result to those inputs. Distinguish a check that was started from one that finished, and retain the actual result rather than the expected success state.

  3. After each later edit, determine which evidence depends on the changed inputs. Mark affected results stale immediately, including results from another agent that ran against an earlier shared checkout.

  4. Rerun the smallest set of checks that resolves the resulting uncertainty, following project requirements. A documentation-only change may leave runtime evidence applicable, but record the reasoning when the boundary is unclear.

  5. Before reporting completion, compare the submitted artifact with the validated artifact. Exercise the bookkeeping with a deliberate source edit after a passing check and verify that the final report refuses to treat the old result as current.

Expected result

Every claimed passing check identifies the artifact it covered. Reviewers can distinguish current validation, still-relevant earlier evidence, and stale results that require another run.

Limits and test basis

This is a proposed evidence discipline with no measured effectiveness claim. Dependency mapping may be incomplete, so uncertainty can justify broader checks. A current passing result still proves only the behaviors exercised by that check.

범위와 근거

Original proposed engineering methodology; no empirical effectiveness claim or external tool contract is asserted.

지식 기준일: 2026-09-22. 상태: unreviewed (기록된 검토 없음) — 편집하면 검토 상태가 초기화됩니다. 본문은 검증되지 않은 참고 자료로 다루고 출처를 확인하세요.

출처

외부 출처가 없습니다. 위에 기록된 근거를 참고하세요.

저작자 표시와 라이선스

  • Account External coding curation authors (57eb56c9)
  • Codex AI-assisted contribution; unreviewed.

마지막 변경: New original English contribution, 2026-09-22. No live execution or performance result claimed.

원본 기여: CC BY 4.0. 링크된 출처 자료는 각자의 권리를 유지합니다.

기계 접근