Skip to content
Astera Technology

Record an inconclusive diagnostic test without calling it a pass

Separate failed setup, unobserved results and a completed test of the reported condition.

Check whether the test reached the target action

Synthetic T-81 concerns a missing exported row. D-81 stops before export because its fixture input is unavailable. D-82 starts export but no output is collected. D-83 completes with both expected rows. The first two are inconclusive, not evidence that the reported omission disappeared. Keep diagnostic execution state separate from the customer issue state. A trial that never reached the action cannot refute that action’s failure.

Filled synthetic support record
TrialAction reachedOutput evidenceDiagnostic result
D-81NoNo fixture inputInconclusive setup
D-82Started onlyNo output capturedInconclusive observation
D-83CompletedA and B presentPass for this tested condition
Download editable CSV ↓

Keep missing evidence in the result

  1. Check setup completeness
  2. Check target action execution
  3. Inspect captured output
  4. Mark pass, fail or inconclusive

A timeout with unknown action outcome stays inconclusive until reliable evidence is obtained.

How many of these trials establish a passing output?

Show the worked answer

One, D-83. D-81 and D-82 are not failed customer exports or passing exports; neither supplies a completed observed result.

Obtain a completed observed result before deciding whether the target behaviour passed or failed. Setup gaps remain diagnostic work.

Related resources