Execute the appropriate test suite (unit, Gherkin, e2e, smoke) and return structured results. Use during Phase 3 (e2e test verification), Phase 4 (red baseline verification), Phase 5 (contract type compilation), Phase 6 (API/Web/integration slices), Phase 7 (smoke tests against deployment), and on resume (re-validate test state). Trigger when running tests, checking test status, or verifying test baselines.
Execute tests and return structured results for the orchestrator.
| Type | Command |
|---|---|
| Unit (TypeScript) | cd src/api && npm test |
| Gherkin | npx cucumber-js |
| E2E | npx playwright test --config=e2e/playwright.config.ts |
| Smoke | npx playwright test --grep @smoke |
| All | npm run test:all |
aspire describe --format Json (or the Aspire MCP list_resources tool) to check resource statusaspire start + aspire wait api --status healthy + aspire wait web --status healthyaspire logs <resource> (or list_console_logs) to diagnoselist_console_logs for resource stdout/stderr around failure timelist_structured_logs for OpenTelemetry log entrieslist_traces to find the failing request's distributed tracelist_trace_structured_logs with the trace ID for full request lifecycleType: unit | gherkin | e2e | smoke | all
Pass: <count>
Fail: <count>
Flaky: <count>
Verdict: GREEN | RED | FLAKY
Failed tests:
- <test name>: <error message>
When tests fail against the Aspire environment:
1. list_resources → Are all resources Running + Healthy?
2. list_console_logs(resource) → Any errors in stdout/stderr?
3. list_traces(resource) → Find the trace for the failing request
4. list_trace_structured_logs → Full trace lifecycle with all spans
5. execute_resource_command → Restart a resource if stuck
aspire start (auto-stops previous)