Add Playwright Tests for Core Dashboard Flows

Aberta
#185 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
55/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
playwright, typescript
Domínio
testing

Direção de pesquisa

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.

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

Descrição

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
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.