Generate test coverage reports for Xcode projects & hook it into CI.

Projects that use Slather

Project	Coverage
Parsimmon
VENCore
DAZABTest
TBStateMachine

Installation

Add this line to your application's Gemfile:

gem 'slather'

And then execute:

$ bundle

Or install the gem:

gem install slather

Usage

Enable test coverage by ticking the "Gather coverage data" checkbox when editing a scheme:

To verify you're ready to generate test coverage, run your test suite on your project, and then run:

$ slather coverage -s --scheme YourXcodeSchemeName path/to/project.xcodeproj

If you use a workspace in Xcode you need to specify it:

$ slather coverage -s --scheme YourXcodeSchemeName --workspace path/to/workspace.xcworkspace path/to/project.xcodeproj

If you use a different configuration for your tests:

$ slather coverage -s --scheme YourXcodeSchemeName --configuration YourBuildConfigurationName path/to/project.xcodeproj

If your configuration produces a universal binary you need to specify a specific architecture to use:

$ slather coverage -s --arch x86_64 --scheme YourXcodeSchemeName --configuration YourBuildConfigurationName path/to/project.xcodeproj

For multiple modules

If you want to run some modules, but not all (like modules created by CocoaPods) you can do it like this:

$ slather coverage --binary-basename module1 --binary-basename module2 path/to/project.xcodeproj

You can also add it to the .slather.yml file as an array:

binary_basename:
  - module1
  - module2

Setup for Xcode 5 and 6

Run this command to enable the Generate Test Coverage and Instrument Program Flow flags for your project:

$ slather setup path/to/project.xcodeproj

General Usage Notes

Commandline Arguments Win

When using both a config file (.slather.yml) and providing arguments via the commandline, the arguments will take precedence over the matching setting in the config file.

ignore always wins over source-files

When defining both files that should be ignored (--ignore, ignore) and source files to include (--source-files, source_files), the ignore list is checked first. If the file being scanned matches a glob in the ignore list, it will not be included. In this case, the source_file list is not checked.

If the file being scanned is not in the ignore list, and source_file has been defined, the source_file list is checked. If the source file matches a glob, it will be included.

CI Integration

Usage with Codecov

Login to Codecov (no need to activate a repository, this happens automatically). Right now, slather supports Codecov via all supported CI providers listed here.

Make a .slather.yml file:

# .slather.yml

coverage_service: cobertura_xml
xcodeproj: path/to/project.xcodeproj
scheme: YourXcodeSchemeName
configuration: TestedConfiguration
source_directory: path/to/sources/to/include
output_directory: path/to/xml_report
ignore:
  - ExamplePodCode/*
  - ProjectTestsGroup/*

And then in your .travis.yml, circle.yml (or after test commands in other CI providers), call slather after a successful build:

# .travis.yml

before_install: rvm use $RVM_RUBY_VERSION
install: bundle install --without=documentation --path ../travis_bundle_dir
after_success: 
  - slather
  - bash <(curl -s https://codecov.io/bash) -f path/to/xml_report/cobertura.xml -X coveragepy -X gcov -X xcode

# circle.yml

test:
  post:
    - bundle exec slather
    - bash <(curl -s https://codecov.io/bash) -f path/to/xml_report/cobertura.xml -X coveragepy -X gcov -X xcode

Private repo? Add -t :uuid-repo-token to the codecov uploader. Read more about uploading report to Codecov here

Usage with Coveralls

Login to Coveralls and enable your repository. Right now, slather supports Coveralls via Travis CI, CircleCI, Jenkins, Teamcity, Buildkite, and Bitrise.

Make a .slather.yml file and specify the CI Service you're using:

# .slather.yml

ci_service: circleci | travis_ci | travis_pro | jenkins | buildkite | teamcity
coverage_service: coveralls
xcodeproj: path/to/project.xcodeproj
scheme: YourXcodeSchemeName
ignore:
  - ExamplePodCode/*
  - ProjectTestsGroup/*

And then in your .travis.yml or circle.yml or github-action.yml, call slather after a successful build:

# .travis.yml

before_install: rvm use $RVM_RUBY_VERSION
install: bundle install --without=documentation --path ../travis_bundle_dir
after_success: slather

# circle.yml

test:
  post:
    - bundle exec slather

# github-action.yml
  myjob:
    steps:
      - run: |
          bundle config path vendor/bundle
          bundle install --without=documentation --jobs 4 --retry 3
      - name: Extract branch name
        shell: bash
        run: echo "##[set-output name=branch;]$(echo ${GITHUB_REF#refs/heads/})"
        id: get_branch
      - run: bundle exec slather
        env:
          GIT_BRANCH: ${{ steps.get_branch.outputs.branch }}
          CI_PULL_REQUEST: ${{ github.event.number }}
          COVERAGE_ACCESS_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Usage with Travis CI Pro

To use Coveralls with Travis CI Pro (for private repos), add following lines along with other settings to .slather.yml:

# .slather.yml

ci_service: travis_pro
coverage_access_token: <YOUR ACCESS TOKEN>

The coverage token can be found at Coveralls repo page. Or it can be passed in via the COVERAGE_ACCESS_TOKEN environment var.

Cobertura

To create a Cobertura XML report set cobertura_xml as coverage service inside your .slather.yml. Optionally you can define an output directory for the XML report:

# .slather.yml

coverage_service: cobertura_xml
xcodeproj: path/to/project.xcodeproj
scheme: YourXcodeSchemeName
source_directory: path/to/sources/to/include
output_directory: path/to/xml_report
ignore:
  - ExamplePodCode/*
  - ProjectTestsGroup/*

Or use the command line options --cobertura-xml or -x and --output-directory:

$ slather coverage -x --output-directory path/to/xml_report

Static HTML

To create a report as static html pages, use the command line options --html:

$ slather coverage --html --scheme YourXcodeSchemeName path/to/project.xcodeproj

This will make a directory named html in your root directory (unless --output-directory is specified) and will generate all the reports as static html pages inside the directory. It will print out the report's path by default, but you can also specify --show flag to open it in your browser automatically.

By default, the generated HTML will reference locally hosted assets (js, css). You can specify the --cdn-assets to specify that you prefer for the generated HTML to use externally hosted assets. This can be useful if publishing the HTML file as a build artifact.

TeamCity Reporting

To report the coverage statistics to TeamCity:

$ slather coverage --teamcity -s --scheme YourXcodeSchemeName

Coverage for code included via CocoaPods

If you're trying to compute the coverage of code that has been included via CocoaPods, you will need to tell CocoaPods to use the Slather plugin by adding the following to your Podfile.

plugin 'slather'

You will also need to tell Slather where to find the source files for your Pod.

# .slather.yml

source_directory: Pods/AFNetworking

Custom Build Directory

Slather will look for the test coverage files in DerivedData by default. If you send build output to a custom location, like this, then you should also set the build_directory property in .slather.yml

Building in a workspace

Include the --workspace argument or add workspace to .slather.yml if you build your project in a workspace. For example:

$ slather coverage --html --scheme YourXcodeSchemeName --workspace path/to/workspace.xcworkspace path/to/project.xcodeproj

Contributing

We’d love to see your ideas for improving this library! The best way to contribute is by submitting a pull request. We’ll do our best to respond to your patch as soon as possible. You can also submit a new GitHub issue if you find bugs or have questions. :octocat:

Please make sure to follow our general coding style and add test coverage for new features!

Contributors

• @tpoulos, the perfect logo.
• @ayanonagon and @kylef, feedback and testing.
• @jhersh, CircleCI support.
• @tarbrain, Cobertura support and bugfixing.
• @ikhsan, html support.
• @martin-key and @troyfontaine, Github Actions support.