ultraqa

Automated QA cycling executes tests, builds, and lints based on specified goals, verifies results, and repeats the cycle until quality criteria are met. It handles interactive testing and architectural diagnosis to ensure continuous code quality improvement.

Autonomous QA cycling automates a continuous workflow that executes tests, builds, lints, and type checks. It parses user-defined goals, verifies execution results, and fixes issues as needed, repeating until the target quality criteria are satisfied.

Goal-based execution parses and executes targets based on user input, ensuring targeted quality checks. You activate the process using a command with a flag like `--tests` to specify your objective, and the system runs the appropriate build and test tools.

Yes, appropriate build and test tools must be installed in your environment to execute the automated QA cycle. The system requires these tools to run tests, builds, lints, and type checks, and then verifies their results to track progress and outcomes.

Yes, interactive testing is supported via a subagent for complex scenarios. The system provides observability and state tracking through detailed logs, allowing you to monitor progress and diagnose architectural issues during the quality assurance cycle.

The cycle continues executing tests, builds, and lints until quality criteria are met. If it keeps failing, check the detailed logs and state tracking to identify persistent issues, or use the interactive testing subagent for architectural diagnosis of complex failures.