Skip to content

Commit 2a35392

Browse files
committed
Update analytics-test-failure-classification documentation to include remark capability and video embed
1 parent 71e04dd commit 2a35392

File tree

1 file changed

+20
-6
lines changed

1 file changed

+20
-6
lines changed

docs/analytics-test-failure-classification.md

Lines changed: 20 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,9 @@ slug: analytics-test-failure-classification/
4040
}}
4141
></script>
4242

43+
import VideoEmbed from '../src/component/videoEmbed';
44+
45+
4346
# Failure Categorization AI - Test Intelligence
4447

4548
LambdaTest Analytics uses Failure Categorization AI to classify test failures into different categories. This helps in identifying the root cause of failures and improving test automation efficiency. The AI model analyzes the test execution data and categorizes the failures based on various parameters such as environment, browser, OS, and failure type. This allows you to focus on the most critical issues and prioritize your testing efforts.
@@ -48,17 +51,28 @@ LambdaTest Analytics uses Failure Categorization AI to classify test failures in
4851

4952
1. You should have an active LambdaTest account.
5053
2. This feature is available for users with the HyperExecute or App / Web Automation subscription plan.
51-
3. You should run at least 10 tests on the LambdaTest automation platform.
52-
4. You should have access to the LambdaTest Insights platform.
53-
5. You can see the failure categorization AI on creating a dashboard in the Insights section.
54-
6. Click on the `Create New` button to create a new dashboard.
55-
7. Choose any of the available widgets and add them to the dashboard.
56-
8. Click on the widget drill down to see the failure categorization AI.
54+
3. You should add the `remark` capability in your test script to enable the Failure Categorization AI. The `remark` capability is used to add comments or notes to the test execution data. This helps in providing additional context to the AI model and improves the accuracy of the failure categorization.
55+
56+
Here is the link to the documentation for the remark capability:
57+
* [Web Automation](https://www.lambdatest.com/support/docs/appium-lambdatest-hooks/#adding-custom-status--remark)
58+
* [App Automation](https://www.lambdatest.com/support/docs/appium-lambdatest-hooks/#adding-custom-status--remark)
59+
60+
4. You should have at least one test failure in your test execution data. The AI model requires a minimum of one test failure to categorize the failures. If there are no test failures, the AI model will not be able to categorize the failures.
61+
5. You should have access to the LambdaTest Insights platform.
62+
6. You can see the failure categorization AI on creating a dashboard in the Insights section.
63+
7. Click on the `Create New` button to create a new dashboard.
64+
8. Choose any of the available widgets and add them to the dashboard.
65+
9. Click on the widget drill down to see the failure categorization AI options.
5766

5867
## What is Failure Categorization AI?
5968

6069
The test failure categorization AI is a machine learning model that classifies test failures into different categories. The AI model uses various parameters such as environment, browser, OS, and failure type to categorize the failures. This helps in identifying the root cause of failures and improving test automation efficiency.
6170

71+
<VideoEmbed
72+
src="https://share.synthesia.io/embeds/videos/4a1bbc2e-6a78-4a31-86e8-1c7d3649d3b1"
73+
title="Exploring Custom Widgets for Dashboards in Lambdatest Insights"
74+
/>
75+
6276
For the first failure as a user you will need to select the type of failure from the list of categories available. The categories are as follows:
6377
- **Product Bug:** This category is used when the failure is due to a bug in the product being tested. This could be a UI issue, a functional issue, or any other type of bug that affects the product's functionality.
6478
- **Test Automation Bug:** This category is used when the failure is due to a bug in the test automation code. This could be a script issue, a framework issue, or any other type of bug that affects the test automation process.

0 commit comments

Comments
 (0)