fix: update E2E container rebuild instructions for clarity and efficiency across multiple documentation files

This commit is contained in:
GitHub Actions
2026-02-07 23:47:30 +00:00
parent f6b03f8330
commit f1782a574d
7 changed files with 27 additions and 14 deletions

View File

@@ -10,7 +10,20 @@ description: 'Strict protocols for test execution, debugging, and coverage valid
### PREREQUISITE: Start E2E Environment
**CRITICAL**: Always rebuild the E2E container before running Playwright tests:
**CRITICAL**: Rebuild the E2E container when application or Docker build inputs change. If changes are test-only and the container is already healthy, reuse it. If the container is not running or state is suspect, rebuild.
**Rebuild required (application/runtime changes):**
- Application code or dependencies: backend/**, frontend/**, backend/go.mod, backend/go.sum, package.json, package-lock.json.
- Container build/runtime configuration: Dockerfile, .docker/**, .docker/compose/docker-compose.playwright-*.yml, .docker/docker-entrypoint.sh.
- Runtime behavior changes baked into the image.
**Rebuild optional (test-only changes):**
- Playwright tests and fixtures: tests/**.
- Playwright config and runners: playwright.config.js, playwright.caddy-debug.config.js.
- Documentation or planning files: docs/**, requirements.md, design.md, tasks.md.
- CI/workflow changes that do not affect runtime images: .github/workflows/**.
When a rebuild is required (or the container is not running), use:
```bash
.github/skills/scripts/skill-runner.sh docker-rebuild-e2e