Skip to content

Test RCA - Triaging Tests

This guide describes how CloudAEye intelligently identifies the underlying cause of test failures.

Overview

Triaging test failures is a critical task for all software teams. It involves identifying the owner of each failing test, assigning them the task of resolving it, and confirming the fix in the next test cycle. This process requires considerable effort, and as the codebase and teams expand, the complexity of managing test failures grows as well. It’s a challenge faced universally across industries, not limited to any specific field. Sometimes, developers are responsible for triaging, while other times, it’s handled by QA teams. Regardless of who takes it on, both agree: support is needed to streamline this process and reduce the mental and logistical workload it demands.

Intelligent Grouping

By grouping tests based on underlying test failure cause, CloudAEye helps to identify the underlying cause.

Test RCA - Triaging

This reduces cognitive load. And saves significant amount of time.


Types of Causes

CloudAEye automates the detection of many other common use-cases such as library related failures, dependent service failures, tests spanning multiple repositories, etc.

Test RCA - Failure Causes

CloudAEye can intelligently identify and summarize failures across tests. By leveraging GenAI, we streamline this process.

Service Failure

CloudAEye can detect service failures. It shows the root cause and proposed fix for the service failure. This saves time during triaging.

Test RCA - Service Failure