Debugging & RCA from logs
Analyzing Failed Test Case Logs and Filler Analysis in ContextQA
Finding the reason why a test case failed can help you quickly spot issues and improve your workflow. Follow these steps to analyze logs and perform filler analysis for a failed test case using ContextQA.
Introduction
We’ll walk through the process of viewing the run history, exploring test logs, and using filler analysis features to determine the root cause of failed test cases.
Click the failed test case run to open its details.
You’ll land on the Run History page. This page lists all past runs for your test case and highlights failures.
Review the AI logs, AI result, network logs, and console log sections.
This page gives you detailed log information, allowing you to dig into what happened during the test case execution.
Watch the video recording to replay the test and visually identify where things went wrong.
Use the Trace View to follow each test step.
Trace View lets you check which step worked successfully and which failed, providing a clear view of the execution flow.
Find the Preview button in the test case screen and click it.
Clicking Preview shows you both the failure’s root cause and recommendations for resolving the issue.
Review the detailed analysis, including failure step reasoning, suggestions, and visual evidence.
You’ll see specific advice and supporting visuals to help you understand the context of the failure.
Check for the EA Root Cause section for a deep dive into why the test failed.
This includes a breakdown of all failure details so you can address the issue more effectively.
Look for available immediate fixes and follow the recommended steps to resolve the problem quickly.
Conclusion
By systematically analyzing logs and filler analysis details for failed test cases, you can find problems faster and keep your tests running smoothly. Use the visual cues and suggested fixes to save time and reduce manual troubleshooting. ContextQA’s robust tools make root cause analysis and test maintenance easy and efficient.
Last updated