Skip to content

Run custom E2E groups after smoke tests #5225

Description

@JayDoubleu

Custom E2E groups could start alongside smoke tests. With deployment reuse, they could also start after smoke tests or group planning were skipped.

Related changes are combined into fewer PRs for review. Earlier PRs and test results remain as historical evidence.

Current position

Item Status and evidence
Current implementation PR #5255
Earlier PRs PR #5226, PR #5256
Completion Merging PR #5255 into main closes this issue.
Position Ordering and success guards implemented and validated in a branch run.
Earlier CI 260 workflow tests passed for PR #5226.
Earlier Azure validation 3 extended cases passed. At ae9314e5, the custom group started four seconds after smoke completed. All three extended cases, 23 smoke tests and cleanup passed.

Scope

  • Require successful smoke tests and group planning before custom groups start.
  • Preserve intentional deployment reuse and block failed, cancelled or skipped prerequisites.

Remaining work

  • Merge the reviewed ordering correction.

Related work

Parent: #5119.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinge2e-testsE2E testsworkflowsGitHub workflows (CI/CD)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions