axiom-analyze-test-failures

Flaky Swift tests in CI are typically caused by race conditions, missing @MainActor isolation, or shared mutable state. Analyze the test source files to detect improper async waiting and parallel execution races to resolve these intermittent failures.

Concurrency violations in Swift test suites stem from missing async confirmations, lack of @MainActor isolation, and shared mutable state. These timing-dependent bugs cause tests to fail randomly when executed concurrently in CI pipelines.

Diagnose Swift test crashes by integrating system diagnostic reports with your test source files. This triage process identifies the root cause of test-generated crashes and detects flaky test patterns like missing concurrency isolation.

Yes, you can scan a repository's test files to identify missing async confirmation handlers and other flaky test patterns. This requires access to test source files and system diagnostic logs to perform comprehensive failure triage.

Identify shared mutable state by scanning test suites for common flaky test patterns including concurrency violations and improper async waiting. Targeting test files within the repository isolates the exact tests suffering from parallel execution races.

Automated flaky test detection requires access to test source files and system diagnostic logs. It targets Swift-specific patterns like missing @MainActor isolation and cannot diagnose failures without adequate system diagnostic reports for crash analysis.