Run the Playwright end-to-end specs in CI
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, javascript, nextjs, nodejs, playwright, typescript
Research direction
Read .github/workflows/ci.yml and frontend/e2e/README.md, then inspect the named specs and frontend/e2e/open-edition.config.ts. Run the current CI checks and the Playwright specs to identify failures on main; add a CI job with the requested backend/frontend setup, Chromium caching, and failure artifact upload. Done when the job meets the runtime target, passes node scripts/check-boundary.js, and the pull request explains the failure-on-purpose check and any quarantined specs.
Written by the indexing model from the issue text.
Description
frontend/e2e/ has Playwright specs (open-edition.spec.ts, matchmaking-preferences.spec.ts, dashboard-layout.spec.ts), but .github/workflows/ci.yml never runs them. CI only runs lint, Jest and next build, so a page that builds but breaks in the browser passes CI.
What to do
- Add a CI job that starts the backend with
CODEARENA_RUNNER=localand a throwawayJWT_SECRET, starts the frontend, and runs the specs withfrontend/e2e/open-edition.config.ts(seefrontend/e2e/README.md). - Install only Chromium to keep the job fast, and cache the Playwright browsers.
- Upload the Playwright report as an artifact when the job fails.
- Fix or quarantine any spec that is already failing on
main, with a note in the pull request explaining which and why.
Definition of done
- The new job is green on
mainand turns red when you break a page on purpose (say how you checked in the pull request). - Runtime stays under about 10 minutes.
node scripts/check-boundary.jspasses.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sennaicodes/codearena
-
Add issue and pull request templatesMay be free again @franciscorodr26 claimed this 19 days ago, and no pull request is open. Opendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
sennaicodes/codearena#13 · 1 comment ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 45/100
sennaicodes/codearena#34 ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 35/100
sennaicodes/codearena#33 ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 45/100
sennaicodes/codearena#32 ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 38/100
sennaicodes/codearena#31 ·
All issues in sennaicodes/codearena
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
micromatch/picomatch#243 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
b310-digital/teammapper#1515 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
c1overzz/dsh-bili-scroll#153 ·
Maintainers usually reply within 1 day
-
01 type: bug 21 status: confirmed 41 lvl: easy 62 scope: viewer
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day