Install and Configure Playwright for the Dashboard

Abierto
#184 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, node.js, playwright, typescript
Área
devtools, testing

Línea de trabajo

Start with the root package.json and workspace setup to see how dependencies, scripts, and checks are configured; then inspect the Node server startup and test database options. Add the Playwright configuration, deterministic test data setup, smoke test, and ignored artifact paths described in the issue. Done means the smoke test runs against a test database and the listed typecheck, test, and lint commands pass.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement good first issue

Goal

Install and configure Playwright for the dashboard E2E suite so npm run test:e2e runs a browser test locally.

Background

The README claims Codra uses "Playwright browser tests", but Playwright is not installed and no config exists. This sub-issue sets up the foundation; the actual flows are covered in sibling sub-issues.

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

What to Build

  • Install @playwright/test as a dev dependency in the root workspace
  • Create playwright.config.ts at the repository root with baseURL: http://localhost:3000
  • Configure the webServer option to launch Codra's Node server against a test database, or document a pre-started server workflow
  • Create a seeded test data strategy (seeded jobs, repos, findings) so tests are deterministic
  • Add a test:e2e script to package.json
  • Add test-results/ and playwright-report/ to .gitignore

Done When

  • npm run test:e2e launches Playwright and opens a browser against the local server
  • One smoke test passes (e.g. landing page renders the login screen)
  • Config uses a test database so runs do not touch real data
  • New artifacts are gitignored
  • npm run typecheck, npm test, and npm run lint all pass
Lenguaje dominante
TypeScript
Estrellas
125
Forks
23
Merge medio
2 d 13 h
PR fusionados (30 d)
12

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de devarshishimpi/codra

Todos los issues de devarshishimpi/codra

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.