noCV
BTEST-101 · Find failure causes

Record first-attempt results separately from rerun results

Practice briefTaskFoundational

A green rerun erases the original failure from the summary.

Focused work estimate
1h + prerequisites
Priority in the scenario
Medium
Engineering practice
Test reporting

Estimated field mix

  • Quality engineering100%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

Review it, then add it to your workspace.

The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.

Project context

A fictional web team reruns red builds until they pass. Shared clocks, leaked state, and unawaited work make failures hard to trust.

Setup prerequisites

  • Create a small local application with three deliberately flaky tests using synthetic data and local endpoints.

Preceding work

No earlier ticket is required. Complete the project setup above.

Acceptance criteria

  • Persist attempt number and original outcome.
  • Link retries to the same test identity.
  • Show initial failure counts separately from final status.

Implementation constraints

  • Exclude screenshots or payloads containing real user data.

Verification to include

  • Record fail-then-pass history.
  • Ensure duplicate reporter delivery does not double-count attempts.

Deliverables

  • Attempt-aware result report.

Rollout and recovery

Introduce reporting before changing retry policy; retain original raw fixture results.

Value of the work

For the engineer: Practice controlled diagnosis, isolation, and test reliability measurement.

For the team: Recover useful failure signals and reduce blind reruns without hiding product defects.

Evidence boundaries

Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.

Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.