# Analyzing test automation failure

> Automate end-to-end test failure analysis with Delegate, from root cause identification and Jira defect logging to stakeholder reporting.

## Analyzing test automation failure

**Delegate** can function as a Test Analyst Assistant.

**Delegate** can be used to automate end-to-end test failure analysis, root cause identification, and stakeholder reporting.

* **End-to-end test automation**

**Delegate** goes beyond single test case execution to orchestrate complete testing workflows. It can analyze entire test sets, identify failures, pull diagnostic logs, reconcile data across multiple systems, create defect tickets, and deliver summary reports — all from a single natural language request.

* **External tool integration**

**Delegate** can interact with external applications and systems beyond Test Manager. Assume Accrual Bank has an Accrual Bank app and an Accrual Bank Test Data Viewer app. **Delegate** can access both apps to reconcile expected versus actual data, create Jira bug tickets for the identified issues, and send summary emails via Microsoft Outlook. These integrations transform **Delegate** from a test executor into a complete testing operations platform.

* **Routine creation and scheduling**

After a complex workflow is successfully executed, **Delegate** can save it as a reusable routine. Routines capture the entire sequence of steps, decisions, and integrations so they can be replayed on demand or scheduled to run automatically at defined intervals (for example, every 24 hours). This enables continuous testing without manual intervention.

### Prerequisites
* Complete the one-time setup in [Setting up and running your first test case](installing-delegate-for-the-testing-profile.md) first.
* You have Project Owner or Test Manager role in **UiPath Test Manager**.
* You configured Jira credentials, in **Delegate**, for ticket creation.
* You configured Microsoft Outlook for email delivery.
* The apps you need (for example, the Accrual Bank Test Data Viewer app) are installed and accessible.
* You defined your use case:

```
Accrual Bank runs a suite of 15 automated and manual test cases every 24 hours to validate its loan processing operations. These tests cover loan application submission, approval workflow, interest calculation, repayment scheduling, and compliance reporting. When tests fail, the QA team must quickly identify root causes, reconcile data, log defects, and inform stakeholders. A report must be sent to the QA lead.
```

### How to

#### Step 1 — Access Test Manager test sets

Open **Delegate** and describe the test set you want to analyze. For example: "Check the loan operations test set in Test Manager and tell me which tests failed in the last 24 hours." **Delegate** connects to Test Manager, locates the specified test set, and retrieves the latest execution results.

#### Step 2 — Analyze execution results

**Delegate** filters the execution results to identify failed test cases.
**Delegate** presents a summary showing the number of passed versus failed tests, along with the names and IDs of the failing cases. For each failure, **Delegate** extracts the error message, stack trace (if available), and execution timestamp.

#### Step 3 — Pull logs for failed tests

**Delegate** downloads detailed execution logs for each failed test case.
The logs contain step-by-step execution traces, variable values, screenshot references, and exception details. The logs are stored locally for further analysis and reconciliation.

#### Step 4 — Reconcile data with Test Data Viewer

**Delegate** opens the Accrual Bank Test Data Viewer application and compares the actual test execution data against the expected baseline data.
**Delegate** identifies discrepancies such as missing records, incorrect values, or data synchronization issues. Each discrepancy is documented with the expected value, actual value, and severity assessment.

#### Step 5 — Create Jira tickets

For each verified discrepancy, **Delegate** creates a Jira bug ticket automatically. The ticket includes a title, description, steps to reproduce, severity, and links to the Test Manager execution log and Test Data Viewer comparison screenshot.
**Delegate** assigns the ticket to the appropriate development team based on the component affected.

#### Step 6 — Send summary report

**Delegate** composes a comprehensive summary email and sends it to the QA lead via Outlook. The report includes: total tests executed, pass/fail breakdown, list of failed tests with root cause analysis, Jira ticket references, and recommendations for next steps.

#### Step 7 — Create and schedule a routine

After the workflow is validated, instruct **Delegate** to save it as a routine. For example: "Save this as a routine called Daily Loan Check and schedule it to run every day at 8 AM."

**Delegate** stores the routine in its library and configures the schedule. The routine will execute automatically, performing the full analysis cycle without human intervention.

### Expected Outcomes
* Daily test analysis is fully automated, reducing manual effort from 2–3 hours to zero.
* All test failures are documented in Test Manager with detailed logs and screenshots.
* Jira tickets are created within minutes of failure detection, accelerating defect resolution.
* Stakeholders receive timely email summaries with actionable insights.
* The routine runs autonomously every 24 hours, ensuring continuous quality monitoring.

### Postrequisites
Ask **Delegate** to turn the sequence of steps into a routine. Save the routine and schedule it to run on specific dates or within an interval.