ci(e2e): split backend and frontend smoke/heavy suites, make required with retries (#389) - #465
Merged
Merged
Conversation
… with retries (Epta-Node#389) - Replace monolithic e2e-fullstack (continue-on-error) with 4 decoupled required jobs: - e2e-backend-smoke (registry/list/create: scenario-a-registration) - e2e-backend-heavy (WS/lifecycle: scenario-b|c|full-pipeline|agent-lifecycle) - e2e-frontend-smoke (registry/list/create: agent-registry, task-submission) - e2e-frontend-heavy (WS/lifecycle: task-monitoring, wallet, i18n) - Add path-based detect-changes job (dorny/paths-filter) so frontend-only or backend-only PRs can pass without waiting for unrelated suites (skipped = success) - Configure flake auto-retry: nick-fields/retry@v3 max_attempts 3, 10-15s backoff; Playwright retains retries:2 in config + outer retry for flake tracking - Upload test artifacts for flake tracking (retention 14 days) for all 4 suites - Add required ci-gate aggregator (branch protection should require this single check) which treats skipped as success for path-filtered PRs while failing on any real failure Resolves Epta-Node#389
|
@MarcusDavidG Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
Someone is attempting to deploy a commit to the Jaja's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
2 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.
Summary
Resolves #389
Changes
e2e-fullstack(continue-on-error: true) with 4 decoupled required jobs:e2e-backend-smoke(registry/list/create:scenario-a-registration) — fast smokee2e-backend-heavy(WS/lifecycle:scenario-b|c|full-pipeline|agent-lifecycle)e2e-frontend-smoke(registry/list/create:agent-registry.spec.ts+task-submission.spec.ts)e2e-frontend-heavy(WS/lifecycle:task-monitoring.spec.ts+wallet.spec.ts+i18n.spec.ts)detect-changesjob (dorny/paths-filter@v3) so frontend-only or backend-only PRs can pass CI — skipped e2e jobs count as successnick-fields/retry@v3withmax_attempts: 3, 10-15s backoff; Playwright keepsretries: 2on CI (inplaywright.config.ts) plus outer retrytest-results-*.json+playwright-report)ci-gateaggregator — branch protection should require this single check; it treatsskippedas success for path-filtered PRs while failing on any realfailure/cancelledVerification & Testing
python3 -c "import yaml; yaml.safe_load(open('.github/workflows/ci.yml'))"— YAML OK, jobs: changes, backend, frontend, contracts, e2e-backend-smoke, e2e-backend-heavy, e2e-frontend-smoke, e2e-frontend-heavy, ci-gate, contracts-integrationcd backend && npm run lint && npm test(skipped — pre-existing backend/package.json duplication unrelated to Split backend and frontend e2e smoke suites and make them required in CI #389)cd frontend && npm run lint && npm run build(decoupled, smoke jobs run independently)scenario-avsscenario-b|c|full-pipeline|agent-lifecycle; frontend smoke vs heavy covers all 5 specsContributor Checklist