Root Cause Analysis

Troubleshoot your tests fast, with the information you need, where you need it.

Why root cause?

Tests break. When they do, you need to find the root cause quickly. Is it an application bug? An outdated test? A network delay? Time spent troubleshooting failed tests slows your release cycles and reduces your ROI.

Visually review the test execution

Drill down to diagnose failures

Analyze failures history

VISUALIZE

Capture highlighted screens

Automatically generate screenshots for every test step. Page through highlighted screens to plainly follow the test flow. Compare screens from the most recent run to a prior successful test run to identify divergence.

DIAGNOSE

Deep-dive into logs

Drill into failed tests with the information needed to determine what happened. Get parsed console logs at the relevant test step. Automatically download HAR files to show network activity. View test configuration data.

ANALYZE

Tag failures, view trends

Tag failed runs with reason codes to better understand failure patterns. View failures by test suite to see the frequency by type or historical trends. Use data-driven analyses to inform your testing process improvements.

“[Troubleshooting] is really important because we have many developers working on the same portal. Being able to quickly determine why a test failed, even when someone else wrote it, saves a lot of time.”
Ran Mizrachi
Software Engineering Manager

“We also significantly reduced our cost of quality: The rich information we get allows us to reduce the time to troubleshoot by 80%.”
QA Manager
Fortune 500 Data Management Company