AwesomeRepos
Sign in

Tags / Testing /

Code coverage

Tool that measures which lines or branches of code tests execute.

The 16repositories with this Tag gained +59 net stars in the last 30 days, 2% more than the 30 days before.

0 created in the last 90 days · 2 published a release in the last 30 days · 41K stars in total

All in the Repository Index On Trending

Net stars each day, last 30 days+9 last 7 days

Oct 5, 2026Nov 3, 2026

  • Seed Dataset
  • Rising Admissions

Most net stars, last 30 days

pester/Pester

Pester is the ubiquitous test and mock framework for PowerShell.

+24

40% of the net stars of this Tag

Largest Pace, last 30 days

No other repository gained 2 or more times the net stars of the 30 days before.

Most stars, created in the last 90 days

No other repository with this Tag was created in the last 90 days.

Where the stars went, last 13 weeks

Net stars gained each week. The repositories that gained the most have their own color.

pester/Pester gained 37% of the net stars of this Tag in the last 13 weeks.

pester/Pester, week to Aug 11: +1 net starscoveragepy/coveragepy, week to Aug 11: +4 net starssimplecov-ruby/simplecov, week to Aug 11: +2 net starscoverlet-coverage/coverlet, week to Aug 11: +3 net starspester/Pester, week to Aug 18: +3 net starscoveragepy/coveragepy, week to Aug 18: +3 net starssimplecov-ruby/simplecov, week to Aug 18: +3 net starscoverlet-coverage/coverlet, week to Aug 18: +1 net starsAll other repositories, week to Aug 18: +2 net starspester/Pester, week to Aug 25: +5 net starscoveragepy/coveragepy, week to Aug 25: +1 net starssimplecov-ruby/simplecov, week to Aug 25: +2 net starscoverlet-coverage/coverlet, week to Aug 25: +1 net starsistanbuljs/nyc, week to Aug 25: +1 net starsAll other repositories, week to Aug 25: +4 net starspester/Pester, week to Sep 1: +3 net starscoveragepy/coveragepy, week to Sep 1: +6 net starssimplecov-ruby/simplecov, week to Sep 1: +3 net starsAll other repositories, week to Sep 1: +3 net starspester/Pester, week to Sep 8: +6 net starscoveragepy/coveragepy, week to Sep 8: +2 net starssimplecov-ruby/simplecov, week to Sep 8: +1 net starscoverlet-coverage/coverlet, week to Sep 8: +3 net starspester/Pester, week to Sep 15: +8 net starscoveragepy/coveragepy, week to Sep 15: +2 net starssimplecov-ruby/simplecov, week to Sep 15: +2 net starscoverlet-coverage/coverlet, week to Sep 15: +1 net starsAll other repositories, week to Sep 15: +1 net starspester/Pester, week to Sep 22: +5 net starssimplecov-ruby/simplecov, week to Sep 22: +2 net starsAll other repositories, week to Sep 22: +8 net starspester/Pester, week to Sep 29: +3 net starscoveragepy/coveragepy, week to Sep 29: +1 net starssimplecov-ruby/simplecov, week to Sep 29: +4 net starscoverlet-coverage/coverlet, week to Sep 29: +1 net starsistanbuljs/nyc, week to Sep 29: +1 net starsAll other repositories, week to Sep 29: +2 net starspester/Pester, week to Oct 6: +9 net starscoveragepy/coveragepy, week to Oct 6: +1 net starssimplecov-ruby/simplecov, week to Oct 6: +1 net starscoverlet-coverage/coverlet, week to Oct 6: +2 net starsAll other repositories, week to Oct 6: +1 net starspester/Pester, week to Oct 13: +4 net starscoveragepy/coveragepy, week to Oct 13: +8 net starsistanbuljs/nyc, week to Oct 13: +2 net starsAll other repositories, week to Oct 13: +2 net starspester/Pester, week to Oct 20: +6 net starscoveragepy/coveragepy, week to Oct 20: +4 net starssimplecov-ruby/simplecov, week to Oct 20: +1 net starscoverlet-coverage/coverlet, week to Oct 20: +1 net starsistanbuljs/nyc, week to Oct 20: +1 net starsAll other repositories, week to Oct 20: +1 net starspester/Pester, week to Oct 27: +5 net starscoveragepy/coveragepy, week to Oct 27: +1 net starssimplecov-ruby/simplecov, week to Oct 27: +1 net starscoverlet-coverage/coverlet, week to Oct 27: +3 net starsistanbuljs/nyc, week to Oct 27: +2 net starsAll other repositories, week to Oct 27: +5 net starspester/Pester, week to Nov 3: +8 net starscoveragepy/coveragepy, week to Nov 3: +1 net starscoverlet-coverage/coverlet, week to Nov 3: +3 net stars

Compare growth

2 of 16 repositories: Created more than 2 years ago, with a push in the last 7 days and a GitHub release in the last 30 days. Select a column name to change the order.

#RepositoryStarsGained, 90 daysPace
1jslint-org/jslint

JSLint, The JavaScript Code Quality and Coverage Tool

3.7K+7–
2coveragepy/coveragepy

The code coverage tool for Python

3.4K+32–

Faster than the 30 days before

Net stars of the last 30 days are 2 or more times those of the 30 days before.

No repository with this Tag meets this rule now.

Slower than the 30 days before

Net stars of the last 30 days are 50% or less of those of the 30 days before.

No repository with this Tag meets this rule now.

New in the last 90 days

Created on GitHub in the last 90 days.

No repository with this Tag meets this rule now.

Older than 2 years, still releasing

Created more than 2 years ago, with a push in the last 7 days and a GitHub release in the last 30 days.

  1. jslint-org/jslint3.7K · release today
  2. coveragepy/coveragepy3.4K · release yesterday

Last release more than 180 days ago

The newest GitHub release is more than 180 days old. A repository that never published a release is not in this list.

  1. istanbuljs/nyc5.8K · release 8 months ago
  2. OpenCover/opencover1.3K · release 5 years ago
  3. qiniu/goc873 · release 3 years ago
  4. parroty/excoveralls862 · release last year
  5. jonreid/XcodeCoverage850 · release 6 years ago
All 7 in the table

Top GitHub topics with this Tag

Primary languages

How a repository gets this Tag

An agent reads the description, the GitHub topics, and the start of the README of each repository. It chooses Tags only from the Tag list in the AwesomeRepos source code. For each Tag, it quotes the text. A code check keeps the Tag only when the quote is in that text. The page of each repository shows the quote of each of its Tags. A Tag does not rank repositories. It does not say that one repository can replace another. To report a wrong Tag, use "Report a problem with this page" on the page of the repository.

How the numbers are counted

All numbers come from the Star History of the repositories that have the Tag now. A period is a run of complete UTC days. All numbers on this page count only the repositories that AwesomeRepos shows in lists. A machine computes them each hour.

For each repository, a period counts only when Star History has each of its days, or when the repository was created in the period. Otherwise the table shows "–". The bars of a week with no complete data are grey.

The Pace is the net stars of a period divided by the net stars of the period before. It shows only when Star History covers each day of the period before, with at least 3 net stars a day on average.

The chart at the top adds up the net stars of all the repositories with the Tag. The darker area is the part from the Seed Dataset; the rest is from rising Admissions. A rising Admission comes into the Repository Index because it gained stars quickly. Its Star History before its Admission comes from the Repository Host. Thus the days before many rising Admissions are higher than they were for the repositories in the index at that time. The repositories of the Seed Dataset are a set that does not change.

The releases are the GitHub releases of each repository. The lists and the table do not rank repositories, and they do not say that one repository can replace another.