# When to Use a Test Plan

Use a Test Plan whenever coordinated, repeatable, multi-flow execution is required across devices or environments. Test Plans are ideal for:

1. **Running multiple flows as a unified suite** to ensure end-to-end stability
2. **Pre-release regression cycles** where broad functional coverage is mandatory
3. **Device-specific or OS-specific validation** across real devices, emulators, or browsers
4. **Validating feature bundles or cross-module behaviors** in a single orchestrated run
5. **Integrating automation into CI/CD pipelines** for continuous, versioned quality gates

Test Plans ensure consistency, scalability, and production-grade reliability across evolving application releases.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.drizz.dev/test-plan/when-to-use-a-test-plan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.