aiox-qa

To review test architecture, you can use quality assurance skills to analyze requirements traceability, assess risk profiles, and generate targeted test strategies. This ensures your new feature covers all necessary scenarios and passes quality gate decisions before deployment.

A quality gate decision evaluates code changes against predefined test architecture and risk assessment criteria to determine release readiness. It improves code quality by enforcing evidence requirements, running automated tests, and suggesting code improvements before merging.

Yes, you can integrate test strategy and risk assessment into your workflow using dependencies like git for version control and supabase for backend validation. The quality assurance process supports browser console checks and CodeRabbit reviews to maintain standards.

Requirements traceability and non-functional requirement assessment are performed by mapping user stories to test cases and evaluating risk profiles. This validates that test designs cover security checklists, migration paths, and performance criteria defined in the story template.

Limitations of automated quality gate decisions include the need for specific agent configuration and multiple dependencies like context7 and browser tools. False positive detection is required to prevent blocking valid builds, and full functionality depends on proper setup of test library validation scripts.