team-qa

You can validate acceptance criteria by loading test context from plan.json and running a full QA workflow across unit, integration, browser, and coverage checks. This verifies each completed task against its defined criteria.

The Skill orchestrates end-to-end test automation by coordinating unit, integration, browser, and coverage checks for active changes. It loads test context from plan.json to validate completed tasks against acceptance criteria.

The best way to consolidate unit and browser testing results is to run an orchestrated QA workflow that validates acceptance criteria and produces a single consolidated report. This report includes structured evidence, test results, and any defects requiring follow-up.

Yes, you need a plan.json file to run end-to-end test automation because the workflow identifies the active change plan and loads its test context from this file. This context provides the acceptance criteria used to validate completed tasks.

Test automation fails when coverage gates are not met because the QA workflow ensures coverage checks are passed for each active change before completing. This prevents incomplete changes from passing validation and generating a successful consolidated report.

Yes, you can use QA-driven test automation for integration and browser checks together as the workflow orchestrates both alongside unit and coverage checks. It coordinates these suites to validate acceptance criteria and produce evidence-driven reports.