Run Playwright Tests in CI and Update Documentation

Open
#186 0 comments 0 reactions 0 assignees View on GitHub

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

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

enhancement good first issue

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.yml that installs Playwright browsers and runs npm 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.md so 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, and npm run lint all pass
Dominant language
TypeScript
Stars
125
Forks
23
Avg merge
2d 13h
Merged PRs (30d)
12

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devarshishimpi/codra

All issues in devarshishimpi/codra

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.