Run Playwright Tests in CI and Update Documentation

Aberta
#186 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
48/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github-actions, playwright, typescript

Direção de pesquisa

Read .github/workflows/ci.yml, the README quality stack section, and the sibling issues describing the E2E suite; inspect the existing database seeding and npm run test:e2e setup. Add the CI run and update the README, then verify the suite runs reliably within the five minute budget 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

Run the Playwright E2E suite in CI and correct the README's testing claims.

Background

Once the E2E suite exists locally (see sibling sub-issues), it needs to run automatically so regressions are caught, and the README claim about Playwright tests finally becomes true.

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

What to Build

  • Add an E2E job step to .github/workflows/ci.yml that installs Playwright browsers and runs npm run test:e2e
  • Seed the test database in CI before the suite runs
  • Consider a nightly schedule run if the suite is too slow for every push
  • Keep the happy-path CI time impact under 5 minutes
  • Update README.md so the quality stack section accurately reflects Playwright as an active testing tool

Done When

  • CI runs the E2E suite on every push/PR (or on a nightly schedule at minimum)
  • The E2E job passes reliably (no flaky failures in the first week)
  • README.md accurately lists Playwright as part of the testing stack
  • CI pipeline happy-path time stays within the agreed budget
  • 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.