Run Playwright Tests in CI and Update Documentation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, playwright, typescript
- Domain
- ci-cd, documentation, testing
Research direction
Read .github/workflows/ci.yml, the README quality stack section, and the sibling issues describing the E2E suite; inspect the existing database seeding and npm run test:e2e setup. Add the CI run and update the README, then verify the suite runs reliably within the five minute budget and the listed typecheck, test, and lint commands pass.
Written by the indexing model from the issue text.
Description
Goal
Run the Playwright E2E suite in CI and correct the README's testing claims.
Background
Once the E2E suite exists locally (see sibling sub-issues), it needs to run automatically so regressions are caught, and the README claim about Playwright tests finally becomes true.
This sub-issue is part of the parent issue: Playwright E2E test suite for core dashboard flows.
What to Build
- Add an E2E job step to
.github/workflows/ci.ymlthat installs Playwright browsers and runsnpm run test:e2e - Seed the test database in CI before the suite runs
- Consider a nightly schedule run if the suite is too slow for every push
- Keep the happy-path CI time impact under 5 minutes
- Update
README.mdso the quality stack section accurately reflects Playwright as an active testing tool
Done When
- CI runs the E2E suite on every push/PR (or on a nightly schedule at minimum)
- The E2E job passes reliably (no flaky failures in the first week)
- README.md accurately lists Playwright as part of the testing stack
- CI pipeline happy-path time stays within the agreed budget
-
npm run typecheck,npm test, andnpm run lintall pass
- Dominant language
- TypeScript
- Stars
- 125
- Forks
- 23
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 12
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a 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 devarshishimpi/codra
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
devarshishimpi/codra#178 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
devarshishimpi/codra#176 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 4/5 3-5 days Newbie friendliness 55/100
devarshishimpi/codra#185 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 4/5 3-5 days Newbie friendliness 58/100
devarshishimpi/codra#184 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 3/5 1-2 days Newbie friendliness 62/100
devarshishimpi/codra#183 ·
Maintainers usually reply within 1 day
All issues in devarshishimpi/codra
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hemilabs/ui-monorepo#2711 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
code-yeongyu/senpi#6929 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 72/100
lingdojo/kana-dojo#34261 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
embedpdf/embed-pdf-viewer#1116 ·
Maintainers usually reply within 1 day
-
current task
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Sunday-School-Software/Sunday-School-Scheduler#87 ·
Maintainers usually reply within 1 day