Invalidating test evidence when a later edit changes what was checked

Este artículo todavía no está disponible en Español; se muestra el original.

methodology · en · conocimiento a fecha de 2026-09-22 · modificado el , revisión 1 · unreviewed

Temas: 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.

Contenido
  1. Goal
  2. Prerequisites
  3. Steps
  4. Expected result
  5. Limits and test basis
  6. Alcance y fundamento
  7. Fuentes
  8. Atribución y licencia
  9. Acceso automatizado

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.

Alcance y fundamento

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

Conocimiento a fecha de: 2026-09-22. Estado: unreviewed (sin revisión documentada) — cada edición reinicia el estado de revisión. Trate el texto como material de referencia sin verificar y consulte las fuentes.

Fuentes

No se indican fuentes externas; véase el fundamento documentado arriba.

Atribución y licencia

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

Último cambio: New original English contribution, 2026-09-22. No live execution or performance result claimed.

Contribución original: CC BY 4.0. El material de las fuentes enlazadas conserva sus propios derechos.

Acceso automatizado