Install and Configure Playwright for the Dashboard

Open
#184 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
58/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, node.js, playwright, typescript
Domain
devtools, testing

Research direction

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.

Written by the indexing model from the issue text.

Description

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