Add test coverage checklist, report template, and stack matrix for ecommerce project
- Created a test coverage checklist to ensure comprehensive testing of backend and frontend components. - Added a test report template to standardize reporting on test execution results and gaps. - Introduced a test stack matrix to guide the selection of testing tools and frameworks for backend and frontend. - Established a skill for repairing failing tests, including a failure triage checklist and a test repair template. - Documented recommended MCP stack for ecommerce development with FastAPI and React/Next.js. - Developed a detailed README outlining the project structure, agent capabilities, and recommended workflows. - Compiled a comprehensive workflow guide detailing step-by-step commands for project setup, testing, and SEO implementation.
This commit is contained in:
+28
@@ -0,0 +1,28 @@
|
||||
# TEST-REPAIR.md Template
|
||||
|
||||
## 1. Initial Failure State
|
||||
- Failing suites
|
||||
- Failing commands
|
||||
- Main error categories
|
||||
|
||||
## 2. Root Cause Analysis
|
||||
- Backend causes
|
||||
- Frontend causes
|
||||
- Environment causes if any
|
||||
|
||||
## 3. Fixes Applied
|
||||
- Code fixes
|
||||
- Test fixes
|
||||
- Config or fixture fixes
|
||||
|
||||
## 4. Rerun Results
|
||||
- Commands rerun
|
||||
- Passing suites
|
||||
- Remaining failures
|
||||
|
||||
## 5. Blockers
|
||||
- Anything still preventing green status
|
||||
|
||||
## 6. Recommended Next Step
|
||||
- Whether to continue fixing
|
||||
- Whether to adjust architecture, fixtures, or test tooling
|
||||
Reference in New Issue
Block a user