Generate code coverage reports for Objective-C Xcode projects with HTML and Cobertura XML output.
XcodeCoverage is a tool that generates code coverage reports for Objective-C projects in Xcode. It instruments your code to measure which parts are exercised by unit tests and produces HTML and Cobertura XML reports. The tool helps developers identify untested code areas while excluding Apple SDKs and allowing custom file exclusions.
Objective-C developers working on iOS or macOS projects in Xcode who need to measure and report on their unit test coverage. It's particularly useful for teams requiring coverage metrics for quality assurance or compliance purposes.
Developers choose XcodeCoverage because it provides a simple, integrated solution specifically for Objective-C coverage that works natively with Xcode's build system. Unlike generic coverage tools, it handles Xcode project structure and offers customizable exclusions while generating both human-readable and machine-processable reports.
Code coverage for Xcode projects (Objective-C only)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Tailored for Objective-C in Xcode, with seamless integration into build settings and schemes, as shown by the included xcconfig file and support for post-action scripts in the README.
Generates both HTML reports for human review and Cobertura XML for CI/CD pipelines, providing flexibility in how coverage data is consumed and reported.
Allows exclusion of specific files and directories via an .xcodecoverageignore file, enabling teams to ignore third-party libraries or generated code, as detailed in the README with examples.
Supports automation through Xcode scheme post-actions, allowing coverage reports to be generated automatically after unit test runs, simplifying the workflow for developers.
Explicitly stated in the README that Swift coverage is not supported, making it unsuitable for modern projects that include Swift code and limiting its relevance in current iOS/macOS development.
Requires adding run scripts to build phases, configuring xcconfig files, and ensuring correct target selection, which can be complex and error-prone, as highlighted in the installation warnings.
When installed via CocoaPods, files are not visible in Xcode and script modifications may be overwritten on updates, reducing flexibility and control, as noted in the README.