Install and Configure Playwright for the Dashboard

Offen
#184 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
58/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
javascript, node.js, playwright, typescript
Bereich
devtools, testing

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
TypeScript
Sterne
125
Forks
23
Ø Merge
2 T. 13 Std.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus devarshishimpi/codra

Alle Issues in devarshishimpi/codra

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.