You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ai-test-failure-analysis.md
+4-23
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
id: rca
3
-
title: What is AI-Powered Test Failure Analysis in HyperExecute
4
-
hide_title: true
3
+
title: AI-Powered Test Failure Analysis in HyperExecute
4
+
hide_title: false
5
5
sidebar_label: AI-Powered Root Cause Analysis
6
6
description: This documentation will help you leverage Root Cause Analysis and Error Classification features in HyperExecute to view different kinds of errors and directly land on corrective measures or fixes.
# AI-Powered Test Failure Analysis in HyperExecute
40
-
---
41
-
42
39
The AI-powered Root Cause Analysis (RCA) and Error Detection for HyperExecute testing helps you to quickly identify various error categories and offers a comprehensive overview of their underlying causes. It analyzes your test logs and identify the root cause of failures, so you can take corrective action quickly and efficiently.
Conventional test failure resolution demands manual analysis of logs and data sources, resulting in substantial delays. These inefficiencies hinder productivity and disrupt software development.
49
-
50
-
HyperExecute's AI-powered Test Failure Analysis seamlessly addresses these challenges, offering a proactive approach to identifying and fixing test case failures along with other benefits including:
45
+
Conventional test failure resolution demands manual analysis of logs and data sources, resulting in substantial delays. These inefficiencies hinder productivity and disrupt software development. HyperExecute's AI-powered Test Failure Analysis seamlessly addresses these challenges, offering a proactive approach to identifying and fixing test case failures along with other benefits including:
51
46
52
47
-**Reduced time to identify and fix failures:** The AI-powered analysis can quickly identify the root cause of failures, so you can take corrective action quickly and efficiently. This can save you a significant amount of time, which can be used to focus on other tasks.
53
-
54
48
-**Improved accuracy of failure analysis:** The AI-powered analysis is more accurate than manual analysis, which can help you to identify and fix failures more effectively. This can lead to a higher quality product.
55
-
56
49
-**Increased productivity of testing teams:** The AI-powered analysis can free up testing teams to focus on other tasks, such as creating new test cases or debugging code. This can lead to a more efficient testing process.
57
50
58
51
## Generate the RCA of your failed Jobs
59
52
60
53
To use the AI-powered Test Failure Analysis feature, simply click on the Failure Analysis" (Beta) tab of your failed Job. Click on the **Generate RCA** Button. This usually takes around 20-30 seconds to generate the RCA.
After categorizing errors, we offer a structured approach to address each failure type. You can efficiently get to the precise corrective measures or **Remedies** recommended alng with **Additional suggestions** for the particular error. This targeted approach expedites the issue resolution process, eliminating unnecessary steps and optimizing efficiency.
The AI-powered Test Failure Analysis feature is a powerful tool that can help you to quickly and easily identify and fix test failures. It offers a number of benefits, including reduced time to identify and fix failures, improved accuracy of failure analysis, and increased productivity of testing teams. If you are looking for a way to improve your testing process, the AI-powered Test Failure Analysis feature is a great option.
description: Learn how to generate the Artifacts for your desired framework and seamlessly interact with artifacts through the HyperExecute UI.
7
7
keywords:
@@ -36,87 +36,52 @@ slug: hyperexecute-artifacts/
36
36
})
37
37
}}
38
38
></script>
39
-
40
-
# Artifacts
41
-
42
39
Artifacts are files generated during test execution, including reports and logs. You can refer to these files for obtaining consolidated information about the executed test cases, and can seamlessly interact with artifacts through the HyperExecute UI.
43
40
44
41
Following the completion of a Job, these artifacts are automatically stored in the **artifacts folder**, distinguishing previous files into **old-artifacts** on subsequent runs while retaining the recent files in artifacts.
45
42
46
-
## Steps to Generate Artifacts
47
-
43
+
## Steps to Generate and Download Artifacts
48
44
Follow the below mentioned steps to generate the Artifacts for your desired framework:
49
45
50
46
**Step 1:** Go to the HyperExecute YAML file
51
47
52
48
**Step 2:** Add the below mentioned parameters in the YAML file to generate the Artifacts
53
49
54
-
```bash
55
-
uploadArtifacts:
56
-
- name: #user defined name of the artifact
57
-
path:
58
-
- #path of the generated artifact
59
-
- name: #user defined name of the artifact
60
-
path:
61
-
- #path of the generated artifact
62
-
```
63
-
64
-
```bash
50
+
```yaml
65
51
uploadArtifacts:
66
-
- name: Executed-Job-Artifacts
52
+
- name: Executed-Job-Artifacts#user defined name of the artifact
67
53
path:
68
-
- src/test/index.html
54
+
- src/test/index.html#path of the generated artifact
69
55
- name: My-Job-Artifacts
70
56
path:
71
57
- src/collect/info.html
72
58
```
59
+
:::note
60
+
- If you are generating multiple artifacts, then it is recommended to use this parameter, [`mergeArtifacts`](/support/docs/deep-dive-into-hyperexecute-yaml/#mergeartifacts) in your YAML, as it will zip all your Artifacts files while downloading from the dashboard.
73
61
74
-
> **Note:** If you are generating multiple artifacts, then it is recommended to use this parameter, `mergeArtifacts` in your YAML, as it will zip all your Artifacts files while downloading from the dashboard.
62
+
- You can replace the Artifacts folder name value with any of the Matrix parameters value.
75
63
76
-
```bash
77
-
mergeArtifacts: true
78
-
uploadArtifacts:
79
-
- name: SrcData
80
-
path:
81
-
- src/test/index.html
82
-
```
83
-
84
-
**Step 3:** Now trigger your job and go to the [HyperExecute](https://hyperexecute.lambdatest.com/hyperexecute/jobs) dashboard.
85
-
86
-
**Step 4:** Click on any of the artifacts generated.
The Auto Healing feature is designed to automatically recover from certain types of failures during the execution of your test scripts. Suppose a test fails because of a network outage. Auto Healing can automatically retry the test. Or, if a test fails because an element on the page is not found, Auto Healing can try to find the element again or log the error and move on to the next test.
82
-
83
-
Auto Healing is especially helpful for flaky tests, which are tests that sometimes pass and sometimes fail even though the underlying code has not changed. Flaky tests can be caused by a variety of factors, such as network outages, resource shortages, or browser crashes. Auto Healing can help you overcome these issues by automatically recovering from failures and retrying your tests.
77
+
Auto Healing employs a dynamic locator strategy that adapts to DOM (Document Object Model) changes in real-time. When an element is initially located, the system records its DOM path and associated attributes. If subsequent attempts to find the element fail due to application updates, the Auto Healing mechanism activates. It analyzes the current DOM structure, comparing it against the previously recorded state, and generates new, contextually relevant locators by intelligently combining element attributes and hierarchical information. This process occurs seamlessly during test runtime, allowing scripts to continue execution despite locator changes. The system continuously monitors the web page for DOM modifications, ensuring sustained test reliability even in the face of frequent application updates.
84
78
85
79
## Benefits of Auto Healing
86
80
Here are some of the benefits of using HyperExecute's Auto Healing feature:
87
81
88
82
-**Reduces the number of Flaky Tests:** Flaky tests are tests that fail intermittently, even though the underlying code has not changed. This can be caused by a variety of factors, such as unstable test environments, network latency, or changes in the browser's rendering engine. Auto Healing can help reduce the number of flaky tests by automatically retrying failed tests a certain number of times.
89
-
90
83
-**Improves Test Reliability:** By automatically recovering from failures, Auto Healing can help improve the reliability of your test suite. This means that you can be more confident that your tests will always pass, even if there are temporary disruptions to the test environment.
91
-
92
84
-**Saves Time and Effort:** Auto Healing can help save you time and effort by automating the process of recovering from failures. This means that you can focus on other tasks, such as developing new tests or fixing bugs.
93
85
94
-
95
86
## Limitations
96
87
While the Auto Healing feature is designed to handle a wide range of issues, there are certain limitations to be aware of:
97
88
98
89
-**Non-recoverable Errors:** Auto Healing cannot recover from certain types of errors, such as WebDriver initialization errors or system-level failures.
99
-
100
90
-**Test Accuracy:** While Auto Healing can reduce test flakiness, it may also mask real issues in your application or test scripts. It's important to review the logs and understand why a test needed healing.
101
-
102
91
-**Performance Impact:** While typically minimal, enabling Auto Healing can have a slight impact on test execution time due to the additional checks and recovery mechanisms.
103
92
104
93
## Best Practices
105
94
By following these best practices, you can use auto healing to improve the reliability and efficiency of your test suite without introducing new risks.
106
95
107
96
- Use a test automation framework that supports Auto Healing. This will make it easier to implement and manage Auto Healing in your test suite.
108
-
109
97
- Identify the types of errors that you want to recover from. Not all errors can be recovered automatically. Focus on recovering from the most common and impactful errors.
110
-
111
98
- Configure auto healing to retry tests a limited number of times. This will help to prevent infinite loops and resource exhaustion.
112
-
113
99
- Log all Auto Healing activity. This will help you understand why tests are failing and to troubleshoot any problems that occur.
114
-
115
100
- Monitor the effectiveness of Auto Healing. Track the number of tests that are healed and the number of false positives. This will help you to determine whether or not auto healing is providing a net benefit.
0 commit comments