test-flakiness

To detect flaky tests in CI runs, this Skill analyzes test logs and results history to identify tests that intermittently pass and fail. It parses JUnit XML and plain text logs to classify outcomes and calculate pass rates.

JUnit XML log parsing classifies intermittent test failures by reading CI run logs and aggregating pass rates per test. This mechanism identifies inconsistent outcomes and provides actionable recommendations for each flaky test.

The best way to manage a flaky test registry for continuous integration is to use a Skill that recommends quarantine or fixes for each flaky test. This maintains reliability and consistency across multiple CI runs.

Yes, you can analyze test reliability using plain text logs from CI workflows. The Skill handles parsing of plain text logs alongside JUnit XML to aggregate pass rates and identify tests with intermittent failures.

You need to scan for test flakiness during the polish phase or after multiple CI runs to maintain high test quality. Scanning ensures continuous integration processes remain reliable and consistent over time.