Root Cause & Impact Analysis
Troubleshoot Test Failures Fast With ContextQA’s Root Cause Analysis
ContextQA makes it easy to spot and fix issues in your automated tests. Its built-in root cause analysis feature helps you quickly understand why tests failed, what went wrong, and how to fix it—reducing headache and saving you time.
Follow these steps to use ContextQA’s root cause analysis feature after a test failure:
Run a test case that includes various task execution methods. For this guide, the password has been intentionally set incorrectly so the login step will fail.
Add a verification step in the test case and enter wrong credentials on purpose. This helps demonstrate how a failure is picked up and analyzed.
Start your test execution. Wait for ContextQA to finish running the test. The run will complete, and you’ll see that the test failed as expected.
Go back to the test case and refresh the page to update the results.
On the top right corner of the test case interface, look for the review icon.
Click this icon to launch ContextQA’s root cause analysis.
ContextQA analyzes the execution video, comparing step-by-step actions with your test steps. It watches for discrepancies and flags where failures occurred.
When the analysis is complete, you’ll see multiple types of feedback:
- The execution video highlights the failure and shows the visible on-screen error message: “invalid login.”
- You’ll also see a screenshot taken at the point of failure.
- The execution video can be reviewed for context.
- ContextQA identifies the root cause and presents it clearly, along with an immediate fix suggestion.
- For this case, ContextQA suggests updating the password field.
In Step 5 of your test case, check for the suggested update. Review the fix provided to ensure your test reflects the correct value going forward.
This structured process gives you a complete understanding of what caused your test to fail and exactly how to resolve it. ContextQA’s root cause analysis saves time, boosts reliability, and keeps your test automation running smoothly.
Try ContextQA on your next test case to see just how fast troubleshooting can be.
Last updated