test: add E2E steps for history delta and tests-changed#30
Merged
Conversation
Add two fixture files (base and changed) with meaningful diffs: - removed/added tests, status flips, duration changes. E2E seeds history with the base, swaps to the changed fixture, then re-runs so the action restores cache and shows deltas. Over successive main runs, flaky/perf/trend features appear.
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add E2E steps that exercise history features (Epic 7) within a single workflow run.
Two fixtures with meaningful diffs (added/removed tests, status flips, duration changes)
are swapped via
cpbetween runs so the action restores cached history and producesdelta comparison and tests-changed output.
Changes
fixtures/e2e-history-base.xml— baseline: 5 tests, 4 passed, 1 failedfixtures/e2e-history-changed.xml— changed: removed test, added test, status flips, slow testHow it works
Both action steps use the same
report-path(same cache key hash). Step 1 seeds thecache with baseline data. The swap step replaces file contents. Step 2 restores history
and shows delta/tests-changed sections in the CI summary.
Over successive main runs, cross-run history accumulates on the "seed baseline" step,
eventually enabling flaky detection (5+ runs), perf regression (3+ runs), and trend
indicators (3+ runs).
Test plan