Add Playwright Browser Tests for Core Dashboard Flows
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, playwright, typescript
- Área
- ci-cd, testing-qa
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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 truepackage.json: Playwright is not indevDependenciestest/e2e/: directory exists but contains no test files.github/workflows/ci.yml: no browser test step@testing-library/reactandjsdomare 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:e2eruns the full browser suite locally - CI runs the E2E suite on every push/PR (or on a nightly schedule at minimum)
-
README.mdaccurately reflects Playwright as an active testing tool -
npm run typecheck,npm test, andnpm run lintall pass
Before Closing
- All E2E flows listed above have at least one test
- No test relies on hardcoded waits (
page.waitForTimeout); usewaitForSelector,waitForResponse, or Playwright's auto-waiting instead - CI does not add more than 5 minutes to the pipeline on the happy path
- Lenguaje dominante
- TypeScript
- Estrellas
- 125
- Forks
- 23
- Merge medio
- 2 d 13 h
- PR fusionados (30 d)
- 12
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de devarshishimpi/codra
-
bug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
devarshishimpi/codra#178 ·
Los mantenedores suelen responder en 1 día
-
bug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
devarshishimpi/codra#176 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
devarshishimpi/codra#186 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
devarshishimpi/codra#185 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue
Dificultad 4/5 3-5 días Aptitud para principiantes 58/100
devarshishimpi/codra#184 ·
Los mantenedores suelen responder en 1 día
Todos los issues de devarshishimpi/codra
Issues similares
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 83/100
gofish-graphics/gofish-graphics#1384 ·
Los mantenedores suelen responder en 1 día
-
adapter bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
Olanetsoft/agent-lookout#353 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
vicharanashala/vibe#1542 ·
Los mantenedores suelen responder en 1 día
-
bug chore P2 size:XS
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
josephfung/curia#2666 ·
Los mantenedores suelen responder en 1 día
-
area: batch
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
inabagumi/shinju-date#7294 ·
Los mantenedores suelen responder en 1 día