Install and Configure Playwright for the Dashboard

Aberta
#184 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
58/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
javascript, node.js, playwright, typescript
Domínio
devtools, testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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
Linguagem predominante
TypeScript
Estrelas
125
Forks
23
Merge médio
2d 13h
PRs com merge (30d)
12

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de devarshishimpi/codra

Todas as issues de devarshishimpi/codra

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.