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:
Vendored
+27
@@ -0,0 +1,27 @@
|
||||
# Test Coverage Checklist
|
||||
|
||||
## Backend
|
||||
- Auth and permission rules.
|
||||
- Catalog reads and writes.
|
||||
- Cart behavior.
|
||||
- Order creation and lifecycle.
|
||||
- Admin operations.
|
||||
- Input validation and error responses.
|
||||
- Critical business logic and edge cases.
|
||||
|
||||
## Frontend
|
||||
- Key page rendering.
|
||||
- Empty, loading, and error states.
|
||||
- User interactions for catalog, cart, checkout, auth, and account.
|
||||
- Admin UI interactions when the repo contains admin code.
|
||||
|
||||
## High-priority ecommerce flows
|
||||
- Add to cart.
|
||||
- Quantity updates and cart totals.
|
||||
- Checkout or lead flow.
|
||||
- Login and protected routes.
|
||||
- Admin create or edit flows.
|
||||
|
||||
## Review quality
|
||||
- Assertions should verify behavior, not just implementation details.
|
||||
- Avoid fragile snapshot-heavy suites unless they truly add confidence.
|
||||
Reference in New Issue
Block a user