Add Playwright Browser Tests for Core Dashboard Flows

Offen
#174 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, playwright, typescript
Bereich
ci-cd, testing-qa

Rechercherichtung

Read package.json, README.md, and .github/workflows/ci.yml to understand the current scripts, claims, and CI setup; inspect the dashboard routes and existing test/e2e directory. Start by mapping the listed user journeys to their route components and available test data. Done means the required flows pass locally and in CI, the suite runs with npm run test:e2e, and the README accurately describes the testing setup.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement good first issue

Summary

README.md claims Codra uses "Playwright browser tests", but Playwright is not installed, there is no playwright.config.ts, and there are zero browser-based tests anywhere in the repository. Dashboard pages have no automated regression coverage, so UI breakage is only caught manually.

This parent issue tracks adding a real Playwright E2E suite under test/e2e that covers the core dashboard user journeys. See sub-issues for each implementation step.

Work Breakdown

  • Sub-issue: Install and configure Playwright with base config and test scripts
  • Sub-issue: Implement core dashboard flow tests
  • Sub-issue: Run E2E suite in CI and fix the README claim

Current State

  • README.md (line 106): lists "Playwright browser tests" as part of the quality stack, but it is not true
  • package.json: Playwright is not in devDependencies
  • test/e2e/: directory exists but contains no test files
  • .github/workflows/ci.yml: no browser test step
  • @testing-library/react and jsdom are installed but no React component tests exist for dashboard pages

Suggested Test Flows

Flow Description
Landing & Auth Visit /, expect login page; simulate GitHub OAuth callback; verify redirect to /dashboard
Dashboard Overview Verify KPI cards render, time range selector works, recent reviews table loads
Jobs List Navigate to /jobs; search by PR title; filter by status; paginate
Job Detail Open a seeded job; verify stepper, findings list (by file / by severity), and diff viewer tab render
Repository Settings Navigate to /repos; toggle a repo enabled/paused; open model settings modal
Stats Page Navigate to /stats; verify charts render without errors
Theme Toggle Toggle between dark/light mode; verify preference persists on reload

Done When

  • Playwright is installed and configured
  • At least the Landing/Auth, Jobs List, Job Detail, and Repository Settings flows have passing tests
  • npm run test:e2e runs the full browser suite locally
  • CI runs the E2E suite on every push/PR (or on a nightly schedule at minimum)
  • README.md accurately reflects Playwright as an active testing tool
  • npm run typecheck, npm test, and npm run lint all pass

Before Closing

  • All E2E flows listed above have at least one test
  • No test relies on hardcoded waits (page.waitForTimeout); use waitForSelector, waitForResponse, or Playwright's auto-waiting instead
  • CI does not add more than 5 minutes to the pipeline on the happy path
Vorherrschende Sprache
TypeScript
Sterne
125
Forks
23
Ø Merge
2 T. 13 Std.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus devarshishimpi/codra

Alle Issues in devarshishimpi/codra

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.