Add Playwright Tests for Core Dashboard Flows

Open
#185 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
playwright, typescript
Domain
testing

Research direction

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.

Written by the indexing model from the issue text.

Description

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
Dominant language
TypeScript
Stars
125
Forks
23
Avg merge
2d 13h
Merged PRs (30d)
12

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devarshishimpi/codra

All issues in devarshishimpi/codra

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.