Run non-release-blocking e2e tests independently#8932
Merged
catalinradoiu merged 1 commit intoJun 19, 2026
Merged
Conversation
Each test suite in the non-blockers nightly was a sequential step in a
single job, so the first failing suite aborted every suite after it. The
suites are independent and only need the uploaded Maestro binary, so a
single failure hid all subsequent ones until the next nightly.
Add an `if: ${{ !cancelled() && steps.<upload>.outcome == 'success' }}`
guard to each test step so every suite runs regardless of earlier suite
failures, gated only on the binary it consumes. The job still ends red
when any suite fails (so the workflow-failure Asana task still fires),
and each failing suite still files its own per-suite Asana task.
https://app.asana.com/1/137249556945/project/1211724162604201/task/1215827024665943
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
catalinradoiu
changed the title
CDRussell
approved these changes
Jun 19, 2026
catalinradoiu
deleted the
fix/cradoiu/run-non-release-blocking-tests-independently
branch
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
3 participants
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.
Task/Issue URL: https://app.asana.com/1/137249556945/project/1211724162604201/task/1215827024665943?focus=true
Tech Design URL (if applicable):
Description
Test suites in the non-release-blocking e2e nightly (
e2e-nightly-non-blockers-suite.yml) ran as sequential steps in a single job. GitHub Actions stops a job at the first failing step, so when an early suite (e.g. Unified Input Field) failed, every suite after it (e.g. Internal Onboarding Flows) was skipped. The suites are independent — each only needs the Maestro binary that was uploaded earlier in the job — so a single failure hid all subsequent failures until the next nightly.This adds an
if: ${{ !cancelled() && steps.<upload>.outcome == 'success' }}guard to each of the five test-suite steps so every suite runs regardless of earlier suite failures, gated only on the binary it consumes.Steps to test this PR
CI passes
UI changes