# Test Plan Reports

Drizz provides comprehensive, production-grade reporting for every Test Plan execution. These reports consolidate functional results, stability metrics, visual evidence, and diagnostic insights giving engineering, QA, and product teams complete visibility into application quality.

### **What Each Test Plan Run Generates**

1. **Run Summary**\
   A high-level overview of total tests executed, pass/fail distribution, duration, environment details, and retry outcomes.
2. **Step-by-Step Execution Logs**\
   Detailed, timestamped logs for every command executed—capturing reasoning, decisions, retries, and validation steps for full traceability.
3. **Screenshots**\
   Visual snapshots taken before and after each test step, enabling fast debugging and comparison against expected UI states.
4. **Video Recording**\
   A full-motion replay of the execution, essential for diagnosing transient UI issues, animation timing, or complex navigation flows.
5. **Error Categorization**\
   Automatic grouping of errors (UI mismatch, navigation failure, device issue, network delay, etc.) to streamline triage and RCA.
6. **Retry Insights**\
   Reports on when and why retries occurred, highlighting flaky or unstable screens.

### **How Reports Help Teams**

1. **Identify Flaky Tests**\
   Spot recurring intermittent failures that impact release confidence and require stabilization.
2. **Monitor Stability Trends**\
   Track long-term quality signals such as success rates, high-failure steps, and device-specific failures.
3. **Track Pass/Fail Rates Across Devices & Environments**\
   Compare test performance across OS versions, real vs. emulator devices, and environment configurations.
4. **Accelerate Debugging & RCA**\
   Combine logs, screenshots, and video to pinpoint root causes quickly—reducing manual analysis effort.
5. **Support Release Readiness Decisions**\
   Provide quantifiable evidence for go/no-go assessments with clean, audit-friendly reporting.


---

# 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/test-plan-reports.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.