Install and Configure Playwright for the Dashboard

未关闭
#184 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
58/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
javascript, node.js, playwright, typescript
领域
devtools, testing

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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
主要语言
TypeScript
星标
125
派生
23
平均合并
2 天 13 小时
30 天内合并 PR
12

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

devarshishimpi/codra 的其他 Issue

查看 devarshishimpi/codra 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。