ВяткинАртём
2817cf8dc6
- 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.
662 B
662 B
name: "Ecommerce Test Repair" description: "Fix failing backend and frontend tests, rerun them, and write .ai/TEST-REPAIR.md with results and blockers." agent: "shop-fullstack-fastapi-react" Repair the current test failures.
Requirements for this run:
- Read .ai/TEST-REPORT.md first if it exists.
- Inspect actual failing test output before making changes.
- Before serious backend or frontend edits, create a timestamped snapshot in .backup/ and do not modify older backup entries.
- Fix the underlying code or the tests depending on root cause.
- Rerun the affected suites.
- Create or update .ai/TEST-REPAIR.md.
- Do not weaken tests just to make them pass.