Add Playwright Tests for Core Dashboard Flows

Ouverte
#185 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
55/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
playwright, typescript
Domaine
testing

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
TypeScript
Étoiles
125
Forks
23
Merge moyen
2 j 13 h
PR mergées (30 j)
12

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de devarshishimpi/codra

Toutes les issues de devarshishimpi/codra

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.