Skip to content

fix(ci): fail the run when any suite has failing tests - #15

Merged
saqibmanan merged 2 commits into
mainfrom
fix/ci-fail-on-test-failures
Sep 29, 2026
Merged

saqibmanan merged 2 commits into
mainfrom
fix/ci-fail-on-test-failures

Conversation

@saqibmanan

Copy link
Copy Markdown
Contributor

Closes #12.

Why

Every suite's pytest step runs with continue-on-error: true so all reports get produced. That also made each job green regardless of results. The most recent E2E run (PR #13, 2026-09-28) had shard 2 = 1 failed and shard 3 = 7 failed, both ✅.

Change

  • scripts/suite_summary.py returns 1 when any suite has failed/errored tests (missing report or all-skipped still returns 0 — path-filtered suites don't produce one).
  • Test Summary records that into TESTS_FAILED and a final step fails the run, after the table and combined report are written.

Heads-up

Current E2E has 8 real failures on dev, so the first E2E run after this merges will go red. That's the point — those were already failing, just hidden.

Verified

Script against fixture reports: failing → 1, passing → 0, missing → 0. Workflow YAML parses.

Every pytest step is continue-on-error, so shards went green with 1-7
failed tests. Test Summary now fails the run from the real JSON counts.

Refs #12
@saqibmanan
saqibmanan merged commit e87f9fc into main Sep 29, 2026
12 checks passed
@saqibmanan
saqibmanan deleted the fix/ci-fail-on-test-failures branch September 29, 2026 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

E2E shards report success despite dozens of failing tests; one test file is never collected

1 participant