julian
17c08e6392
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24) - apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004) - apps/web: React 19 + Vite 8 (ESM) - libs/shared/api-interface: Zod contract base - Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit - WDS artifacts: - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs) - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact) - Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md - AGENTS.md + README.md como entrada para devs/agentes Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
121 lines
3.5 KiB
Markdown
121 lines
3.5 KiB
Markdown
---
|
|
name: 'step-02-discover-tests'
|
|
description: 'Find and parse test files'
|
|
nextStepFile: '{skill-root}/steps-c/step-03-quality-evaluation.md'
|
|
outputFile: '{test_artifacts}/test-review.md'
|
|
---
|
|
|
|
# Step 2: Discover & Parse Tests
|
|
|
|
## STEP GOAL
|
|
|
|
Collect test files in scope and parse structure/metadata.
|
|
|
|
## MANDATORY EXECUTION RULES
|
|
|
|
- 📖 Read the entire step file before acting
|
|
- ✅ Speak in `{communication_language}`
|
|
|
|
---
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Follow the MANDATORY SEQUENCE exactly
|
|
- 💾 Record outputs before proceeding
|
|
- 📖 Load the next step only when instructed
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: config, loaded artifacts, and knowledge fragments
|
|
- Focus: this step's goal only
|
|
- Limits: do not execute future steps
|
|
- Dependencies: prior steps' outputs (if any)
|
|
|
|
## MANDATORY SEQUENCE
|
|
|
|
**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
|
|
|
|
## 1. Discover Test Files
|
|
|
|
- **single**: use provided file path
|
|
- **directory**: glob under `{test_dir}` or selected folder
|
|
- **suite**: glob all tests in repo
|
|
|
|
Halt if no tests are found.
|
|
|
|
---
|
|
|
|
## 2. Parse Metadata (per file)
|
|
|
|
Collect:
|
|
|
|
- File size and line count
|
|
- Test framework detected
|
|
- Describe/test block counts
|
|
- Test IDs and priority markers
|
|
- Imports, fixtures, factories, network interception
|
|
- Waits/timeouts and control flow (if/try/catch)
|
|
|
|
---
|
|
|
|
## 3. Evidence Collection (if `tea_browser_automation` is `cli` or `auto`)
|
|
|
|
> **Fallback:** If CLI is not installed, fall back to MCP (if available) or skip evidence collection.
|
|
|
|
**CLI Evidence Collection:**
|
|
All commands use the same named session to target the correct browser:
|
|
|
|
1. `playwright-cli -s=tea-review open <target_url>`
|
|
2. `playwright-cli -s=tea-review tracing-start`
|
|
3. Execute the flow under review (using `-s=tea-review` on each command)
|
|
4. `playwright-cli -s=tea-review tracing-stop` → saves trace.zip
|
|
5. `playwright-cli -s=tea-review screenshot --filename={test_artifacts}/review-evidence.png`
|
|
6. `playwright-cli -s=tea-review network` → capture network request log
|
|
7. `playwright-cli -s=tea-review close`
|
|
|
|
After capturing `trace.zip`, prefer Playwright's newer trace CLI for local or downloaded artifact analysis:
|
|
|
|
- `npx playwright trace open <trace.zip>` to start a trace session
|
|
- `npx playwright trace actions --grep="expect"` to jump to the failing assertion
|
|
- `npx playwright trace action <n>` / `trace snapshot <n> --name after` for root-cause details
|
|
- `npx playwright trace close` when done
|
|
|
|
> **Session Hygiene:** Always close sessions using `playwright-cli -s=tea-review close`. Do NOT use `close-all` — it kills every session on the machine and breaks parallel execution.
|
|
|
|
---
|
|
|
|
## 4. Save Progress
|
|
|
|
**Save this step's accumulated work to `{outputFile}`.**
|
|
|
|
- **If `{outputFile}` does not exist** (first save), create it using the workflow template (if available) with YAML frontmatter:
|
|
|
|
```yaml
|
|
---
|
|
stepsCompleted: ['step-02-discover-tests']
|
|
lastStep: 'step-02-discover-tests'
|
|
lastSaved: '{date}'
|
|
---
|
|
```
|
|
|
|
Then write this step's output below the frontmatter.
|
|
|
|
- **If `{outputFile}` already exists**, update:
|
|
- Add `'step-02-discover-tests'` to `stepsCompleted` array (only if not already present)
|
|
- Set `lastStep: 'step-02-discover-tests'`
|
|
- Set `lastSaved: '{date}'`
|
|
- Append this step's output to the appropriate section of the document.
|
|
|
|
Load next step: `{nextStepFile}`
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
|
|
|
|
### ✅ SUCCESS:
|
|
|
|
- Step completed in full with required outputs
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
|
|
- Skipped sequence steps or missing outputs
|
|
**Master Rule:** Skipping steps is FORBIDDEN.
|