e2e-dev-stack
Run Playwright E2E specs against the running dev stack to test uncommitted changes. Use when adding or changing an E2E spec or verifying a user-facing flow end to end.
来源信息
- 仓库
- HiEventsDev/Hi.Events
- 最近来源活动
- 2026年10月16日 09:30
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 4,155
- Forks
- 755
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- e2e-dev-stack
- description
- Run Playwright E2E specs against the running dev stack to test uncommitted changes. Use when adding or changing an E2E spec or verifying a user-facing flow end to end.
# Run E2E specs against the dev stack
The hermetic e2e stack bakes source into images and `docker compose up` never rebuilds them, so test uncommitted changes against the dev stack. From `e2e/`:
```bash
E2E_BASE_URL=https://localhost:8443 MAILPIT_URL=http://localhost:8025 E2E_SAAS_MODE=true npx playwright test <spec>
```
## Prerequisites
- `E2E_SAAS_MODE=true` is required: the dev stack requires email verification, and the fixture only confirms through Mailpit in SaaS mode.
- A queue worker must be running to deliver the verification emails: `docker compose -f docker-compose.dev.yml exec -d backend php artisan queue:work`.
- Superadmin-dependent specs need a one-time `php artisan dev:bootstrap --email=superadmin@e2e.test --password='SuperAdminPass123!'`.
- Seating and box office specs need `APP_LICENCE_KEY=development` in `backend/.env`.
- `@stripe` specs need `STRIPE_SECRET_KEY`, the backend's `STRIPE_WEBHOOK_SECRET` and `E2E_STRIPE_CONNECT_ACCOUNT_ID` exported. Webhooks are handled by the queue worker, so poll for the result.
See "Against the running dev stack" in `e2e/README.md` for more.
在 GitHub 查看