Replay Test Strategy

Audience: Stella Ops test-automation and QA engineers validating that scans replay deterministically. Scope: How we prove that recorded scan bundles replay bit-for-bit across tool/definition updates and environments, and how drift is surfaced rather than masked.

Imposed rule: Replay tests must use frozen inputs (SBOM, advisories, VEX, feeds, policy, tools) and fixed seeds/clocks; any non-determinism is a test failure.

1. Goals

2. Test layers

  1. Golden replay: take a recorded bundle (SBOM/VEX/feeds/policy/tool hashes) and rerun; assert hash equality for SBOM, findings, VEX, logs. Fail on any difference.
  2. Feed drift guard: rerun bundle after feed update; expect differences; ensure drift is surfaced (hash mismatch, diff report) not silently masked.
  3. Tool upgrade: rerun with new scanner version; expect stable outputs if no functional change, otherwise require documented diffs.
  4. Policy change: rerun with updated policy; expect explain trace to show changed rules and hash delta; diff must be recorded.
  5. Offline: replay in sealed mode using only bundle contents; no network access permitted.

3. Inputs

4. Determinism settings

5. Assertions

6. Tooling

7. Outputs

8. Reporting

9. Checklists

References