qa-sweep

End-to-end QA sweeps are automated by coordinating browser automation, API smoke checks via curl, and database verification with psql. This approach applies manifest-driven phases across domains like auth, dashboard, and orders to catch regressions with an auditable trail.

Manifest-driven resume flow for QA testing persists progress across conversation boundaries and long-running test sessions. You need it when orchestrating comprehensive UI tests and data validations that span multiple domains and may require pausing or resuming execution.

API smoke checks and database validations run alongside UI test automation by coordinating curl commands for API health checks and psql for database verification. This comprehensive testing ensures user journeys are validated across all application layers.

Browser automation validates user journeys across multiple application domains including auth, dashboard, accounts, orders, activities, and admin. Deterministic Chrome MCP automation drives these tests to ensure comprehensive end-to-end coverage.

Fixes found during QA sweeps are documented through structured fix commits and PR-ready reports. This strict per-fix commit discipline maintains an auditable trail of issues and resolutions across all tested domains.

Orchestrating QA tests with a manifest-driven approach requires initializing a QA branch and establishing baselines from Phase 0. Limitations include dependency on Chrome MCP for browser automation and the need for persistent manifests to track progress across conversation boundaries.