Merge pull request LambdaTest#2456 from surishubham/stage

Merge pull request LambdaTest#2455 from sandeepyadav-lt/prod-rca

Author: surishubham

assets/images/analytics/test-intelligence-ai-test-rca-hyperexecute.webp

@@ -43,17 +43,14 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
     }}
 ></script>
 
-AI Root Cause Analysis (AI RCA) in <BrandName /> Analytics automatically analyzes failed tests to identify probable root causes and provides actionable insights to improve test stability and reduce debugging time. This AI-powered feature accelerates your debugging process by eliminating manual investigation and providing instant, comprehensive failure analysis.
+AI Root Cause Analysis (AI RCA) in <BrandName /> Analytics uses advanced AI-powered LLM technology to automatically analyze failed tests and identify their root causes. Instead of manually sifting through logs and error messages, AI RCA provides:
 
-## What is AI Root Cause Analysis?
+- **Intelligent root cause identification** - distinguishes between primary causes and cascading symptoms
+- **Actionable fixes** - specific recommendations to resolve issues
+- **Error timelines** - chronological sequence of events leading to failures
+- **Trend analysis** - identifies recurring patterns across test executions
 
-AI RCA is an intelligent feature that uses advanced machine learning algorithms to automatically analyze test failures and identify their root causes. Instead of manually sifting through logs and error messages, AI RCA provides:
-
-- **Automated failure analysis** that runs immediately when tests fail
-- **Intelligent root cause identification** distinguishing between primary causes and cascading symptoms
-- **Actionable steps to fix** with specific fixes and recommendations
-- **Historical trend analysis** to identify recurring issues and patterns
-- **Comprehensive error timelines** showing the sequence of events leading to failures
+<img loading="lazy" src={require('../assets/images/analytics/test-intelligence-ai-test-rca-output.webp').default} alt="RCA Output" width="800" height="400" className="doc_img"/>
 
 ## Prerequisites for AI RCA
 
@@ -63,9 +60,123 @@ AI RCA is an intelligent feature that uses advanced machine learning algorithms
 4. **Test Failures**: AI RCA requires at least one test failure to generate analysis. The system learns from your test execution patterns.
 5. **Access to Insights**: You should have access to the <BrandName /> Insights platform under **Insights** tab.
 
-## Configuration & Setup
+## RCA Generation Methods
+
+<BrandName /> offers two methods to generate Root Cause Analysis:
+
+- **Automatic RCA**: RCA is generated automatically for failed tests based on your configuration settings. Set it up once in Organization Settings, and RCA runs continuously for matching test failures.
+
+- **Manual RCA**: Generate RCA on-demand for any failed test by clicking the **Generate RCA** button. Useful for investigating specific failures without setting up targeting rules.
+
+:::tip When to Use Each Method
+- Use **Automatic RCA** for continuous monitoring of critical test suites where you want immediate analysis of every failure.
+- Use **Manual RCA** for ad-hoc debugging when you need to investigate a specific test failure without setting up automated rules.
+:::
+
+| Feature | Automatic RCA | Manual RCA |
+|---------|---------------|------------|
+| **Trigger** | Runs automatically when configured tests fail | Click "Generate RCA" button |
+| **Targeting Rules** | Follows Analysis Scope and Intelligent Targeting settings | Any failed test on-demand |
+| **Custom RCA Categories** | ✓ Applied | ✓ Applied |
+| **Special Instructions** | ✓ Applied | ✓ Applied |
+| **Best For** | Continuous monitoring | Ad-hoc debugging |
+
+:::note Shared Configuration
+**Custom RCA Categories** and **Special Instructions** configured in Organization Settings apply to both Automatic and Manual RCA generation. This ensures consistent categorization and analysis context across all RCA results.
+:::
+
+## Generate RCA Manually
+
+You can manually generate RCA for any failed test from the **Test Manager** or **HyperExecute** dashboards.
+
+### From Test Manager (TMS)
+
+<img loading="lazy" src={require('../assets/images/analytics/test-intelligence-ai-test-rca-tms.webp').default} alt="Generate RCA in Test Manager" width="800" height="400" className="doc_img"/>
+
+1. Navigate to **Test Manager** → open a **Test Run**
+2. Go to the **Test Instances** tab
+3. Locate the failed test and click the **Generate RCA** button
+4. View the RCA output with root cause, severity, and recommended fixes
+
+### From HyperExecute
+
+<img loading="lazy" src={require('../assets/images/analytics/test-intelligence-ai-test-rca-hyperexecute.webp').default} alt="Generate RCA in HyperExecute" width="800" height="400" className="doc_img"/>
+
+1. Navigate to **HyperExecute** → open the failed **Job**
+2. Select the **Tasks** tab and expand the failed scenario
+3. Click the **Generate RCA** button next to the failed test
+4. View the generated RCA with actionable insights
+
+### From Insights Dashboard
+
+The Insights dashboard provides aggregated RCA analytics and trend analysis across all your test executions.
+
+<img loading="lazy" src={require('../assets/images/analytics/test-intelligence-ai-test-rca-insights.webp').default} alt="RCA Insights Dashboard" width="800" height="400" className="doc_img"/>
+
+1. Navigate to **Insights** from the <BrandName /> dashboard
+2. Access the **RCA Category Trends** widget to view aggregated data
+3. Click on specific categories to drill down into detailed analysis
+4. Track historical trends to monitor improvement over time
+
+## Understanding RCA Output
+
+When you generate or view an RCA, a detailed analysis panel opens with the following components:
+
+<img loading="lazy" src={require('../assets/images/analytics/test-intelligence-ai-test-rca-output.webp').default} alt="RCA Output" width="800" height="400" className="doc_img"/>
+
+### Error Classification
+
+At the top of the RCA panel, you'll see:
+
+- **Failure Category**: The type of failure (e.g., `App Bug`, `Product Bug`)
+- **Root Cause Type**: The specific error category (e.g., `JavaScriptError`, `Backend Contract Violation`)
+- **Error Summary**: A one-line description of the error with file location
+- **Error Trends (Test)**: Shows how often this specific test has failed recently
+- **Error Trends (Global)**: Shows the error pattern across all tests over time
+
+### Detailed Analysis
+
+Expand this section to see AI-generated insights explaining:
+- Why the component or test failed
+- What the error indicates about the underlying issue
+- The specific file and line number where the error occurred
+
+### Event Timeline
+
+The Event Timeline shows the chronological sequence of events during test execution:
+
+- **✓ Passed steps**: Steps that completed successfully (e.g., "Test Execution Started")
+- **✗ Failed steps**: Steps where issues occurred, tagged as:
+  - **Root Cause**: The primary reason for failure
+  - **Effect**: Secondary failures caused by the root cause
+
+Click **Show/Hide** on any event to expand details including:
+- **Code**: View the relevant source code
+- **Stacktrace**: See the full error stack trace
+- **Assets**: Access screenshots, logs, or other artifacts
+
+### How to Fix It
+
+At the bottom of the RCA panel, you'll find numbered, actionable steps to resolve the issue. These recommendations include:
+- Specific actions to take in your application or test
+- Configuration changes to consider
+- Debugging steps to verify the fix
+
+### Provide Feedback
 
-<img loading="lazy" src={require('../assets/images/analytics/test-intelligence-ai-test-rca-configuration.webp').default} alt="cmd" width="800" height="400" className="doc_img"/>
+Help improve RCA accuracy using the feedback options at the bottom:
+- **Thumbs up/down**: Rate if the analysis was helpful
+- **Suggest Improvements**: Click to open a feedback form where you can:
+  - Adjust the failure category and root cause classification
+  - Provide a custom root cause if the AI classification was incorrect
+  - Add additional context or feedback
+
+
+## Configure Automatic RCA
+
+Set up Automatic RCA to continuously analyze test failures based on your targeting rules.
+
+<img loading="lazy" src={require('../assets/images/analytics/test-intelligence-ai-test-rca-configuration.webp').default} alt="Automatic AI RCA Configuration" width="800" height="400" className="doc_img"/>
 
 ### Step 1: Access Organization Settings
 
@@ -231,110 +342,14 @@ Provide context or specific guidance for the AI to consider during analysis:
 1. Click **Save Configuration** to apply your settings
 2. The settings will be applied to all users in your organization and cannot be modified by individual users or need admin level privileges.
 
-## RCA Output & Interpretation
-
-### Where to View RCA Results
-
-AI RCA results are available in multiple locations across the <BrandName /> platform:
-
-1. **TMS Dashboard**: View RCA results directly in your test execution dashboard
-2. **HyperExecute Dashboard**: Access detailed RCA analysis for HyperExecute jobs
-3. **Insights Dashboard**: Comprehensive RCA analytics and trend analysis
-
-<img loading="lazy" src={require('../assets/images/analytics/test-intelligence-ai-test-rca-insights.png').default} alt="cmd" width="800" height="400" className="doc_img"/>
-
-### Understanding RCA Output
-
-The RCA output provides a unified analysis with:
-
-- **Primary Root Cause**: The main issue identified by AI analysis
-- **Cascading Symptoms**: Secondary issues that contribute to the problem but aren't the primary cause
-- **Severity Level**: High, Medium, or Low severity classification
-- **Error Category**: JavaScript Error, Network Error, Environment Issue, etc.
-
-<details>
-<summary>View Example RCA</summary>
-
-**Example RCA Summary:**
-> **Problem**: Contact creation test fails after 30 seconds  
-> **Root Cause**: Database connection pool is full (10/10 connections used)  
-> **Impact**: New contact requests wait in queue until connections free up  
-> **Fix**: Increase connection pool from 10 to 50 connections
-
-#### Error Timeline
-
-The Error Timeline provides a chronological sequence of events leading to the failure:
-
-**Example Timeline for CRM Contact Creation Test Failure:**
-1. **Test starts** - Navigate to contacts page (1s)
-2. **Fill form** - Enter contact details (3s)  
-3. **Click submit** - Create contact button clicked (4s)
-4. **Connection issue** - Database pool full, request queued (4s)
-5. **Wait timeout** - No connections available (30s)
-6. **Test fails** - "Contact creation timeout"
-
-#### Steps to Fix
-
-Each RCA includes specific, actionable steps to fix with clear implementation guidance:
-
-**Database Connection Issues:**
-- **Quick Fix**: Increase connection pool from 10 to 50
-- **Code**: `spring.datasource.hikari.maximum-pool-size=50`
-- **Test Fix**: Add connection health check before form submission
-
-**Form Submission Failures:**
-- **Quick Fix**: Add retry logic with 3 attempts
-- **Code**: `retry(createContact, { maxAttempts: 3, delay: 2000 })`
-- **Test Fix**: Mock database calls in test environment
-
-**Performance Issues:**
-- **Quick Fix**: Increase timeout to 45 seconds
-- **Code**: `waitForElement('#success-message', { timeout: 45000 })`
-- **Test Fix**: Use lightweight test data
-
-</details>
-
-### RCA Category Trends Widget
-
-The RCA Category Trends widget in Insights enables you to:
-
-1. **View Historical Trends**: See how different RCA categories have evolved over time
-2. **Drill Down Analysis**: Click on specific categories to analyze test failure patterns
-3. **Identify Recurring Issues**: Spot patterns in failure types to prioritize fixes
-4. **Track Improvement**: Monitor the effectiveness of your remediation efforts
-
-<img loading="lazy" src={require('../assets/images/analytics/test-intelligence-ai-test-rca-insights.png').default} alt="cmd" width="800" height="400" className="doc_img"/>
-
 ## Best Practices
 
-### 1. Effective Configuration
-
-- **Start with "All failures"** to get comprehensive coverage, then refine based on your needs
-- **Use specific special instructions** to guide the AI toward your most critical issues
-- **Set up intelligent targeting** to focus on relevant test suites and exclude noise
-- **Create custom RCA categories** to organize and track failure patterns systematically
-
-### 2. Interpreting Results
-
-- **Focus on primary root causes** rather than cascading symptoms
-- **Prioritize high-severity issues** for immediate attention
-- **Use the error timeline** to understand the sequence of events
-- **Apply steps to fix systematically** starting with the most critical fixes
-
-### 3. Continuous Improvement
-
-- **Review RCA accuracy** and provide feedback when possible
-- **Monitor trend analysis** to identify recurring patterns
-- **Update special instructions** based on new insights and requirements
-- **Refine custom RCA categories** to better match your failure patterns and organizational needs
-- **Share RCA results** with your team to improve collective understanding
-
-<!-- ### 4. Integration with Workflow
-
-- **Set up alerts** for high-severity RCA findings
-- **Create tickets** directly from RCA results for systematic tracking
-- **Use RCA data** in sprint planning to prioritize bug fixes
-- **Document successful fixes** to build institutional knowledge -->
+- **Focus on Root Cause events** in the Event Timeline rather than Effect events when debugging
+- **Check Error Trends** to see if this is a recurring issue or a new failure
+- **Use the Code and Stacktrace tabs** to pinpoint the exact location of the error
+- **Follow the "How to Fix It" steps** systematically for faster resolution
+- **Provide feedback** using thumbs up/down to help improve RCA accuracy over time
+- **Monitor trends in Insights** to identify patterns and prioritize fixes
 
 ## Troubleshooting Common Issues