Mobile Testing
.xcresult bundle
Also known as: xcresult, Xcode result bundle
An .xcresult bundle is the result container Xcode and xcodebuild produce for a test run — a directory holding test outcomes, logs, attachments, screenshots and coverage in Apple’s own format rather than in JUnit XML.
Because it is a bundle rather than a flat file, an .xcresult carries far more than a pass/fail list: per-test activity trees, captured screenshots and videos, console logs, and code-coverage data all live inside it. That richness is exactly why it does not map cleanly onto JUnit XML, whose vocabulary stops at suites, cases, failures and durations.
The usual CI workaround is to convert the bundle to JUnit XML with a third-party tool and upload the result, which works but discards the attachments and activity detail that made the bundle worth having. Reading the bundle directly preserves them — Qualflare’s CLI parses .xcresult natively for this reason, so screenshots and step detail survive the trip into reporting.
- A directory bundle, not a file — it carries attachments, logs and coverage.
- Converting to JUnit XML is lossy: attachments and activity detail are dropped.
- Native parsing preserves what the conversion throws away.
Learn more
Related terms
See it in your own test results
Qualflare detects flaky tests, clusters failures by root cause, and scores release risk from the test results you already produce in CI. Start free.
Start free with Qualflare← Back to the testing & observability glossary.
Last reviewed September 10, 2026