Skip to content
One plugin to combine all the plugins across iOS repos
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
DomainDangerPlugin.xcodeproj Fixy Jun 12, 2019
Images Danger Plugin Jun 12, 2019
.gitignore Danger Plugin Jun 12, 2019
Dangerfile.swift Danger Plugin Jun 12, 2019
Gemfile Danger Plugin Jun 12, 2019
Gemfile.lock Danger Plugin Jun 12, 2019
Package.resolved Fixy Jun 12, 2019
Package.swift Fixy Jun 12, 2019 Danger Plugin Jun 12, 2019


Danger-Swift plugin to show the coverage of the modified/created files.


Getting Started

Install DangerSwiftCoverage

Swift Package Manager (More performant)

You can use a "full SPM" solution to install both danger-swift and DangerSwiftCoverage.

  • Add to your Package.swift:
let package = Package(
    products: [
        .library(name: "DangerDeps", type: .dynamic, targets: ["DangerDependencies"]), // dev
    dependencies: [
        // Danger Plugins
        .package(url: "", from: "0.1.0") // dev
    targets: [
        .target(name: "DangerDependencies", dependencies: ["Danger", "DomainDangerPlugin"]), // dev
  • Add the correct import to your Dangerfile.swift:
import DomainDangerPlugin

  • Create a folder called DangerDependencies on Sources with an empty file inside like Fake.swift
  • To run Danger use swift run danger-swift command
  • (Recommended) If you are using SPM to distribute your framework, use Rocket, or similar to comment out all the dev depencencies from your Package.swift. This prevents the dev dependencies to be downloaded and compiled with your framework.


  • Add this to your Dangerfile.swift
import DangerSwiftCoverage // package:

                            minimumCoverage: 50, 
                            excludedTargets: ["DangerSwiftCoverageTests.xctest"])
  • (Recommended) Cache the ~/.danger-swift folder

Gather Coverage

  • Enable "Gather the Coverage" on Xcode


or, on your CI, execute:

xcodebuild test -scheme DangerSwiftCoverage-Package -derivedDataPath Build/ -enableCodeCoverage YES

Custom XCResultBundle path

If you are using the -resultBundlePath parameter on xcodebuild you will need to use:

                            minimumCoverage: 50, 
                            excludedTargets: ["DangerSwiftCoverageTests.xctest"])

Swift Package Manager

From Swift 5.0 you can gather the coverage from SPM with the --enable-code-coverage=true flag For SPM coverage add to your Dangerfile:

Coverage.spmCoverage(minimumCoverage: 50)


This project is licensed under the terms of the MIT license. See the LICENSE file.

You can’t perform that action at this time.