Knowing how your code changes affect coverage is important to prevent bugs and issues. At Codecov, we know that pull/merge requests is one of the most critical parts of the developer workflow when making a code change. As such, we provide tools in the developer workflow via status checks and pull/merge request comments.
However, this isn’t always enough. Our previous pulls page did a good job of showing our user’s coverage information for the pull request, but where it failed was making it easy to drill down into the code to see where and why coverage increased or dropped.
Our new pulls page puts the most relevant information right in front of you and helps to explain why things might have gone awry with coverage. This helps you be more informed and make better decisions about your testing practices.
Coverage information to you upfront
The new Pulls page now drops you into the Impacted Files tab which shows all of the coverage changes of a particular pull/merge request. This makes it easy to locate files that have dropped significant coverage. You can click on each heading to sort the list, letting you control which metrics are most important to you and your team.
Superscript on each tab
Each tab of the new Pulls page shows a superscript representing the number of items in each section. This helps you to quickly compare details and notice unexpected changes. For example, seeing a large number of Indirect Changes can be a sign of a widespread change or missing coverage uploads.
More screenspace
The page was redesigned with space in mind. Now, the in-line file viewers span the entire width so that you can get a full view of your code. This helps to identify and get context on changes that have coverage changes.
Indirect changes tab
The Indirect Changes tab shows you how your pull request affects other parts of the codebase. You can use this tab to identify files that were not changed but may have downstream effects.
Performance improvements
Previously, the Pulls page was not optimized for speed. With the new page, we have made tweaks to ensure that you are getting coverage information as quickly as possible.
- a superscript on each tab representing the number of items in each section so that you can quickly compare details and notice unexpected changes,
- more screenspace for in-file viewing to get a full view of your codebase,
- indirect file changes to see how your code change affects other parts of the codebase,
- and performance improvements to load the page faster and get you the information you need.
What’s next for the Pulls page?
Currently, there are only small changes and tweaks expected from the Pulls page. The most significant change will be to add a file viewer for all your covered files so that you can also see the current state of your codebase.
If you have any feedback or questions, please leave a comment on our feedback board.
