testing

Unit tests and integration tests are selected by detecting your project stack and evaluating the change context. The appropriate testing level is then determined to ensure proper validation coverage across layers.

End-to-end testing is triggered when the detected stack and change context require full validation. The workflow evaluates whether quick-loop or plan-exec-loop scenarios demand broader coverage before prompting human confirmation to proceed.

To get started, select the testing level and stack for your current task. The workflow then coordinates validation accordingly, ensuring decisions are recorded for audit and respect execution rules preventing automatic test runs.

Yes, human confirmation is required before executing tests. The workflow enforces execution rules that prevent automatic test runs unless explicitly authorized, ensuring a human-in-the-loop validation process for all changes.

Yes, the testing strategy applies to both quick-loop and plan-exec-loop scenarios. It coordinates validation across these workflows by applying stack detection and change context to guide the appropriate testing level.

Testing decisions are recorded for audit purposes to maintain a traceable history of validation choices. This ensures accountability when determining unit, integration, or end-to-end testing levels across detected stacks and change contexts.