Merge branch 'LambdaTest:stage' into stage

Author: Manuraj-7

.github/workflows/pr.yml

@@ -8,6 +8,17 @@ on:
     merge_group:
 
 jobs:
+    sonarqube-analysis:
+      runs-on: ubuntu-latest
+      steps:
+        - name: Checkout repo
+          uses: actions/checkout@v4
+
+        - name: SonarQube Analysis
+          uses: SonarSource/sonarqube-scan-action@master
+          env:
+            SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
+            SONAR_HOST_URL: ${{ secrets.SONAR_HOST_URL }}
     build-and-deploy:
       runs-on: ubuntu-20.04
       env:

assets/images/github-oauth-integration/app-installed.webp

@@ -1,6 +1,6 @@
 ---
 id: accessibility-automation-test
-title: Accessibility Testing on HyperExecute using Selenium
+title: Automation Tests with Accessibility Tool using Selenium
 sidebar_label: Selenium
 description: Use LambdaTest Accessibility DevTools to detect and report accessibility issues with automation, following WCAG guidelines.
 keywords:
@@ -129,4 +129,4 @@ Now execute your tests and visit the [Automation Dashboard](https://accounts.lam
 mvn test
 ```
 
-<img loading="lazy" src={require('../assets/images/accessibility-testing/accessibility-automation.png').default} alt="automation-dashboard" className="doc_img"/>
+<img loading="lazy" src={require('../assets/images/accessibility-testing/accessibility-automation.png').default} alt="automation-dashboard" className="doc_img"/>

assets/images/github-oauth-integration/authorize-user.webp

@@ -117,7 +117,44 @@ driver.executeScript(`lambda-testCase-end=${Name of test case}`)
 
 ```
 
-### Capture by NPM Package for WebdriverIO
+### Capture by Playwright reporter 
+
+#### Step 1 - Configure your reporter in YAML
+
+You can capture the test case insights by using the `reporter` configuration in your `YAML` file for capturing and seeing the test cases in our test case widgets on dashboard. 
+
+Here is a link to documentation for setting up the reporter for `PlaywrightJS`: [Click here](/docs/playwright-html-report/#step-1-update-your-playwright-configuration)
+
+#### Step 2 - Add the code to lambdatest-setup file
+
+Once, you have setup the `reporter` then the following code snippet should be added to your `lambdatest-setup.js` config. 
+
+```js title=lambdatest-
+try {
+        const response = JSON.parse(await ltPage.evaluate(
+          (_, data) => {
+            return window.eval(data)
+          },
+          `lambdatest_action: ${JSON.stringify({ action: 'getTestDetails' })}`
+        ))
+
+        if (response?.data?.test_id) {
+          testInfo.annotations.push({
+            type: 'lt_test_id',
+            description: response.data.test_id,
+          })
+          console.log('LambdaTest Test ID:', response.data.test_id)
+        }
+      } catch (err) {
+        console.warn('Could not fetch LambdaTest test details:', err.message)
+      }
+```
+
+#### Step 3 - Execute the tests using HyperExecute
+
+You can now, execute the tests on our `HyperExecute` platform and you can see the results captured in the `Test Case Widgets` on the dashboards.
+
+## Capture by NPM Package for WebdriverIO
 
 You can capture the test case insights by using the NPM Package. You need to add the following `NPM Package` in your test script. Here is the link to the NPM package: [wdio-lambdatest-test-case-analytics-service](https://www.npmjs.com/package/wdio-lambdatest-test-case-analytics-service)
 

assets/images/github-oauth-integration/authorize.webp

@@ -0,0 +1,99 @@
+---
+id: analytics-test-failure-classification
+title: Failure Categorization AI - Test Intelligence
+sidebar_label: Failure Categorization AI
+description: 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.
+keywords:
+  - analytics
+  - test failure classification
+  - test intelligence
+  - failure categorization
+  - AI
+  - machine learning
+  - test automation
+url: https://www.lambdatest.com/support/docs/analytics-test-failure-classification/
+site_name: LambdaTest
+slug: analytics-test-failure-classification/
+---
+
+<script type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify({
+       "@context": "https://schema.org",
+        "@type": "BreadcrumbList",
+        "itemListElement": [{
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.lambdatest.com"
+        },{
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Support",
+          "item": "https://www.lambdatest.com/support/docs/"
+        },{
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Test Overview",
+          "item": "https://www.lambdatest.com/support/docs/analytics-test-failure-classification/"
+        }]
+      })
+    }}
+></script>
+
+import VideoEmbed from '../src/component/videoEmbed';
+
+
+# Failure Categorization AI - Test Intelligence
+
+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.
+
+## Pre-requisites For Failure Categorization AI
+
+1. You should have an active LambdaTest account.
+2. This feature is available for users with the HyperExecute or App / Web Automation subscription plan.
+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.
+
+Here is the link to the documentation for the remark capability: 
+* [Web Automation](https://www.lambdatest.com/support/docs/appium-lambdatest-hooks/#adding-custom-status--remark)
+* [App Automation](https://www.lambdatest.com/support/docs/appium-lambdatest-hooks/#adding-custom-status--remark)
+
+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.
+5. You should have access to the LambdaTest Insights platform.
+6. You can see the failure categorization AI on creating a dashboard in the Insights section.
+7. Click on the `Create New` button to create a new dashboard.
+8. Choose any of the available widgets and add them to the dashboard.
+9. Click on the widget drill down to see the failure categorization AI options.
+
+## What is Failure Categorization AI?
+
+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.
+
+<VideoEmbed 
+  src="https://share.synthesia.io/embeds/videos/4a1bbc2e-6a78-4a31-86e8-1c7d3649d3b1" 
+  title="Exploring Custom Widgets for Dashboards in Lambdatest Insights"
+/>
+
+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:
+- **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.
+- **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.
+- **Environment Issue:** This category is used when the failure is due to an issue with the test environment. This could be a configuration issue, a network issue, or any other type of issue that affects the test environment.
+- **No Action Required:** This category is used when the failure does not require any action. This could be a known issue, a false positive, or any other type of issue that does not require any action from the user.
+
+Once the user selects the category for the first failure, the AI model will learn from the user's selection and will automatically categorize the subsequent failures based on the user's selection. This helps in reducing the manual effort required to categorize the failures and improves the overall efficiency of the test automation process.
+
+## How will the Failure Categorization AI help you?
+
+The failure categorization AI helps you in the following ways:
+
+- **Automated Classification:** The AI model automatically classifies the test failures into different categories, reducing the manual effort required to categorize the failures.
+
+- **Improved Efficiency:** By categorizing the failures, the AI model helps in identifying the root cause of failures and improving test automation efficiency.
+
+- **Prioritization of Testing Efforts:** The AI model helps in prioritizing the testing efforts by identifying the most critical issues that need to be addressed.
+
+- **Better Insights:** The AI model provides better insights into the test execution data, helping you to make data-driven decisions.
+
+
+## Support 
+
+For any queries or issues related to the Failure Categorization AI, please reach out to our [24/7 customer support](mailto:support@lambdatest.com). We are here to help you!