Add Playwright Tests for Core Dashboard Flows

Offen
#185 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
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
55/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
playwright, typescript
Bereich
testing

Rechercherichtung

Start by reading the sibling issue for Playwright setup and the dashboard routes and components for /, /dashboard, /jobs, /repos, and /stats; the payload does not name their files. Then add E2E coverage for the listed flows, using seeded data and a deterministic OAuth stub where needed. Done means all seven flows pass repeatedly, no test uses hardcoded waits, and typecheck, test, and lint pass.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement good first issue

Goal

Implement Playwright E2E tests for the core dashboard user journeys.

Background

With Playwright configured (see sibling sub-issue), the dashboard flows need actual test coverage. This sub-issue implements the tests; CI integration is a sibling sub-issue.

This sub-issue is part of the parent issue: Playwright E2E test suite for core dashboard flows.

Flows to Cover

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

Implementation Guidance

  • Use Playwright's built-in locators (getByRole, getByTestId) over CSS selectors for resilience
  • Add data-testid attributes to key dashboard components where needed
  • Never rely on hardcoded waits (page.waitForTimeout); use waitForSelector, waitForResponse, or Playwright's auto-waiting
  • Auth flow may need a mocked or stubbed GitHub OAuth callback for deterministic tests

Done When

  • At least the Landing/Auth, Dashboard Overview, Jobs List, Job Detail, and Repository Settings flows have passing tests
  • Stats page and Theme toggle flows have passing tests
  • No test uses hardcoded waits
  • Tests are deterministic across repeated local runs
  • npm run typecheck, npm test, and npm run lint all pass
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.