Skip to content

Conversation

@sandeepyadav-lt
Copy link
Contributor

This pull request updates the AI Root Cause Analysis (RCA) documentation to improve clarity, organization, and introduce new features for managing custom RCA categories. The most significant changes include restructuring the setup steps, adding detailed instructions for creating and managing custom RCA categories, and enhancing guidance for providing special instructions to the AI. These updates aim to make the configuration process more intuitive and empower users to better classify and analyze test failures.

Documentation improvements and restructuring:

  • Reorganized the configuration steps for enabling AI RCA, separating the analysis scope configuration into its own step and moving the "Special Instructions" section later in the process for better logical flow.
  • Updated image references to use .webp format for improved loading performance.

New feature documentation: Custom RCA Categories:

  • Added a new step and section detailing how to create, manage, and use custom RCA categories, including best practices, example categories, and status management (Active/Inactive).
  • Updated best practices and workflow recommendations to include creating and refining custom RCA categories for better organization and trend tracking. [1] [2] [3]

Enhanced guidance for AI analysis:

  • Expanded the "Special Instructions" section with more comprehensive example instructions, including environment-specific context, business context, technical constraints, and common false positives to ignore.

These changes make the AI RCA documentation more actionable and user-friendly, supporting more effective root cause analysis and test failure management.

…, configuring analysis scope, and managing custom RCA categories. Added best practices and examples for clarity. atx-6210
…d update documentation to include the new image reference.
@surishubham surishubham merged commit 64c53a8 into LambdaTest:stage Nov 7, 2025
1 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants