Files
johndoe6345789 06c0f9fb5c refactor: move critical flows tests to packages/system_critical_flows
Moved critical user flow tests to proper package structure:
- Created packages/system_critical_flows/ package
- Converted hardcoded e2e/critical-flows.spec.ts to declarative JSON
- Located at packages/system_critical_flows/playwright/tests.json
- 24 critical flows across 10 categories (all @smoke, @critical, @auth, etc.)

Structure:
- packages/system_critical_flows/package.json (package metadata)
- packages/system_critical_flows/playwright/tests.json (24 tests, declarative JSON)
- packages/system_critical_flows/playwright/metadata.json (entity metadata)
- packages/system_critical_flows/README.md (package documentation)
- packages/system_critical_flows/playwright/README.md (test documentation)

This aligns with MetaBuilder architecture:
- Tests are in packages (not root e2e/)
- 100% declarative JSON format
- Integrated with unified test runner
- Follows playwright.schema.json specification
- 95% configuration, 5% code principle

The unified test runner auto-discovers and executes via:
npm run test:e2e (discovers all packages/*/playwright/tests.json)

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2026-01-21 03:44:05 +00:00

19 lines
481 B
JSON

{
"entityType": "playwright",
"package": "system_critical_flows",
"description": "System-wide critical user flow end-to-end tests",
"version": "1.0.0",
"testCoverage": [
"Public discovery & login flows",
"Authentication & session management",
"User dashboard functionality",
"Admin user management",
"Package management",
"Navigation & discovery",
"Error handling",
"User experience",
"System resilience",
"System stability"
]
}