Codecov is the leading code coverage solution for CI/CD pipelines, delivering coverage metrics right into your workflow. It integrates directly with Bitrise to provide valuable insights on code quality in order to allow users to ship healthier code with less risk.
Codecov provides many features that make test coverage more available and actionable to speed up your development process and to deliver high-quality applications.
Some of these features include:
- Coverage changes overlaid with your source code, making it even easier to identify needed test areas.
- Multi-language support so you can use Codecov right out of the box.
- Summary of coverage information directly in your Workflow so that you can add and update tests quickly and effectively.
- Status checks to block underperforming pull requests from being merged.
- Seamless coverage report merging for Workflows that upload multiple reports across jobs.
- Custom coverage information based on groupings using Codecov Flags.
Integrating Codecov with Bitrise ⚓
In order to start using Codecov, you must be generating coverage reports with your preferred coverage tool (for example, Xcode or Gradle).
- Create an account on https://codecov.io.
Go to repository’s Settings tab on Codecov and copy the repository upload token.
- Add the Codecov Step to your Workflow on Bitrise. Make sure you add the Step after the Steps that test and collect coverage.
- Add the Codecov upload token as a secret variable,
CODECOV_TOKEN, and click Add new.
- Click Save and start a new build to get coverage metrics.
Viewing your coverage reports on Codecov ⚓
To view your coverage on Codecov, you can do the following:
- View the URL supplied on the Codecov Step on Bitrise.
- Go to https://codecov.io and navigate directly to the applicable pull request or commit.
- Click on the links provided by Codecov that are available on your code host’s status checks or pull request comment.
What next? ⚓
Now that you have code coverage reports, you can take it to the next level with the following suggestions:
- Set non-blocking status checks to get your developers in the habit of thinking about code coverage.
- Start working towards code coverage by setting status checks to increase overall coverage on every pull request.
- Isolate your coverage reports for different types of tests or different parts of your system with Flags to measure what matters.
- Already using flags and don’t want to run your entire test suite with every Bitrise CI run? Try out Carryforward Flags to measure only what changes.
All Bitrise builds have a build number. The first build of your app is, by default, number 1, and the build number gets incremented with each build. You can also...
Applivery is a mobile app distribution platform for iOS and Android that provides a powerful mobile app management and distribution system to simplify app delivery for both testers and employees,...
Deployment can mean a number of things on Bitrise: you can deploy your app to test devices, or to bitrise.io, with a public install page that you can freely distribute...