test-failure-investigator

To diagnose failing unit tests from CI build logs, you parse test result XML files and aggregate the failing tests with relevant logs to isolate root causes. This structured failure analysis provides actionable diagnostics for the failing component.

The best way to parse test results and analyze per-test logs is using a structured workflow that aggregates failing tests from XML output. This approach surfaces actionable diagnostics by examining per-test and per-suite details across multiple components.

To enable verbose logging for investigating a failing test suite, follow a targeted debugging workflow that guides you through activating logging, running specific test suites, and examining detailed per-test results to isolate the failure.

Yes, you need standard build tooling like cmake and test targets to run tests for log analysis. Accessing a parse_test_results.py utility is also required to parse the test-results XML and surface actionable diagnostics.

Yes, you can use this workflow to investigate failures across multiple components. It analyzes per-test and per-suite results across your build, providing a repeatable investigation workflow to isolate the specific failing component.

CI reports failing tests without clear error details when logs are not properly aggregated with test results. Parsing test result XML files and enabling verbose logging during test execution surfaces the actionable diagnostics needed to identify root causes.