How to Exclude Specific Classes from Code Coverage Reports

Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.

To exclude a class reliably, first identify which tool creates the coverage report and which artifact your CI gate reads. Use a class or type filter where the tool supports one; otherwise filter the source file or path. Then regenerate every report used for decisions and inspect its raw contents and totals. An HTML page can hide a class while a separate XML or LCOV report still counts it.

Understand where the exclusion takes effect

Coverage moves through several stages, and an exclusion at one stage does not automatically apply to the others:

#	Preview	Product	Price
1		GameStop Physical Gift Card	$25.00	Buy on Amazon
2		Xbox Physical Gift Card	$25.00	Buy on Amazon
3		$100 XBOX Gift Card [Digital Code]	$100.00	Buy on Amazon
4		Fortnite Physical Gift Card	$50.00	Buy on Amazon
5		$25 PlayStation Store Gift Card [Digital Code]	$25.00	Buy on Amazon

• Instrumentation: the tool modifies or observes code so it can record execution. An instrumentation exclusion means no data is collected for the matched code.
• Report scope: data may have been collected, but the report generator leaves the class or file out when calculating HTML, XML, or other output.
• Source-line rules: selected lines, methods, or generated regions are ignored while the rest of a file remains eligible.
• Consumer filtering: a CI dashboard or quality service filters a report after it is generated.

Choose the stage that computes the percentage or threshold you care about. JaCoCo, for example, distinguishes agent exclusions from report exclusions; its guidance for removing classes from a report is to configure report generation. See the JaCoCo FAQ.

An exclusion changes measurement, not application behavior: tests can still execute the excluded code. Depending on the tool, removing a class can remove its lines, branches, methods, or other counters from the denominator.

#1 Best Overall

GameStop Physical Gift Card

• Redeemable at US GameStop, EB Games, Babbage's, Electronic Boutique, EBX, Planet X, and Software Etc. stores. Also redeemable online at and GameStop.com and EBGames.com.
• Over 6,100 stores located throughout the United States.
• GameStop. Power to the Players.
• Redemption: Instore and Online
• No returns and no refunds on gift cards.

$25.00

Buy on Amazon

Choose a filter that matches the code and tool

“Class” is not a universal filter unit. Java, Kotlin, .NET, and PHP tools can offer type- or class-oriented rules. Python, JavaScript/TypeScript, and native C/C++ tools generally filter files, paths, or source lines instead.

• Prefer an exact fully qualified type when only one type should be omitted. A simple name may match types in more than one namespace.
• Use a package, namespace, or directory rule for a stable group, such as generated code. Broad rules are easier to maintain but can silently exclude future production code.
• Check what the pattern describes: a compiled class path such as com/acme/model/Dto.class, a source path such as src/Generated/Client.cs, a glob, or a regular expression.
• For Java, nested and inner classes can compile into separate files, commonly named with $ (for example, Outer$Inner.class). Excluding only Outer.class may not exclude them.
• One source file can contain multiple classes; conversely, partial classes or generated files may contribute to one logical type. A file exclusion can therefore be broader than a type exclusion.
• Check case sensitivity and path separators. Some tools normalize paths; others distinguish case or require forward slashes even on Windows.
• Do not assume glob and regex syntax are interchangeable. In globs, * commonly matches characters; regex metacharacters such as . may need escaping.

Compiler-generated and synthetic code may already be handled by a tool’s defaults. Inspect the actual report before adding a broad rule.

Java and Kotlin

JaCoCo with Maven

The JaCoCo Maven report goal accepts include and exclude patterns for class files; its documented wildcards are * and ?. The following is a configuration example using version 0.8.14; use the version managed by your own build rather than treating this as a recommendation to upgrade or downgrade. JaCoCo’s trunk documentation lists a different snapshot version. See the report goal parameters.

<plugin>
  <groupId>org.jacoco</groupId>
  <artifactId>jacoco-maven-plugin</artifactId>
  <version>0.8.14</version>
  <executions>
    <execution>
      <goals>
        <goal>report</goal>
      </goals>
    </execution>
  </executions>
  <configuration>
    <excludes>
      <exclude>com/acme/generated/**</exclude>
      <exclude>com/acme/legacy/LegacyAdapter*</exclude>
      <exclude>com/acme/model/Dto.class</exclude>
    </excludes>
  </configuration>
</plugin>

These are class-file patterns, not Java source globs. If you generate reports with the JaCoCo command-line report tool, apply equivalent exclusions to that invocation too, and ensure every output format uses the intended class files.

Rank #2

Xbox Physical Gift Card

• XBOX GIFT CARD: Buy full digital game downloads, game add-ons, in-game currency, memberships, devices, apps, movies, TV shows, and more.
• DIGITAL GAMES: Choose from hundreds of games, from AAA to indie options. Start playing the moment your most anticipated game is available when you pre-order and pre-download it.
• GAME AD-ONS: Extend the experience of your favorite games with add-ons and in-game currency.
• MOVIES & TV SHOWS: Rent or buy new and popular movies and TV shows from a massive library.
• PERFECT GIFT: Great as a gift for a friend or yourself. Xbox Gift Cards are easy to use, never expire, and give the freedom to pick the gift they want. Enjoy more ways to play without a credit card attached to your Microsoft account.

$25.00

Buy on Amazon

JaCoCo with Gradle

Gradle’s JacocoReport task uses classDirectories as the class-file collection for report generation. Filter that collection in the task that produces the report, as in this Groovy DSL example:

tasks.named('jacocoTestReport') {
    dependsOn test

    classDirectories.setFrom(files(classDirectories.files.collect {
        fileTree(dir: it, exclude: [
            'com/acme/generated/**',
            'com/acme/legacy/LegacyAdapter*.class',
            '**/*$Generated*.class'
        ])
    }))
}

In Kotlin DSL, the equivalent pattern is:

tasks.jacocoTestReport {
    dependsOn(tasks.test)

    classDirectories.setFrom(
        files(classDirectories.files.map {
            fileTree(it) {
                exclude(
                    "com/acme/generated/**",
                    "com/acme/legacy/LegacyAdapter*.class",
                    "**/*\$Generated*.class"
                )
            }
        })
    )
}

The Gradle JaCoCo task does not automatically depend on test. Add a dependency as shown, or arrange for test to finalize with the report task, depending on your build. See the Gradle JaCoCo plugin guide and the JacocoReport API. For Android or multi-variant builds, apply filtering to the relevant variant’s class directories; the JVM report task should not be assumed to cover Android instrumented-test outputs.

Kotlin with Kover

Kover supports class and package exclusion rules, and its documentation says exclusions take precedence over inclusions. Configuration names have changed across plugin releases, so check the documentation for the version in your build. An example pattern is:

kover {
    reports {
        filters {
            excludes {
                classes("com.acme.generated.**")
                classes("com.acme.dto.Dto")
            }
        }
    }
}

See the Kover Gradle plugin documentation.

.NET

Coverlet type, file, and attribute filters

Coverlet’s MSBuild integration supports type filters, file filters, and attribute filters. Its type-filter form is [Assembly-Filter]Type-Filter; multiple filters are comma-separated. In that syntax, * matches zero or more characters and ? makes the preceding character optional. Exclusions take precedence over inclusions. For example:

Rank #3

$100 XBOX Gift Card [Digital Code]

• THE PERFECT GAMING GIFT — Buy an XBOX Gift Card for yourself or a friend and let them choose the games, add‑ons, subscriptions, and accessories they want most.
• USE FOR GAMES & CONTENT — Redeem for thousands of digital XBOX games, from backward compatible classics to the latest new releases, plus DLC and in‑game currency.
• GAME PASS READY — Apply your balance toward XBOX Game Pass Ultimate to play new titles on day one* and access a library of hundreds of high‑quality console games.
• PRE‑ORDER & PRE‑INSTALL GAMES — Use your balance to pre‑order and pre‑download upcoming titles so you’re ready to play the moment they launch.
• NO FEES OR EXPIRATION — XBOX Gift Cards never expire and have no service fees, so your balance is ready whenever you are.

$100.00

Buy on Amazon

dotnet test \
  /p:CollectCoverage=true \
  /p:CoverletOutputFormat=cobertura \
  /p:Exclude="[MyProduct]MyProduct.Generated.GeneratedClient,[*]MyProduct.Legacy.LegacyAdapter"

If generated code should always be excluded regardless of the build’s reporting policy, a source attribute can express that intent:

using System.Diagnostics.CodeAnalysis;

[ExcludeFromCodeCoverage]
public sealed class GeneratedClient
{
}

Coverlet also accepts attribute filters, for example /p:ExcludeByAttribute="Obsolete%2cGeneratedCodeAttribute". Use a type or file filter when the same source may be measured under different policies; an attribute is a better fit when exclusion is an intrinsic property of generated code. See Coverlet MSBuild integration. The Microsoft Testing Platform integration exposes corresponding options including --coverlet-exclude, --coverlet-exclude-by-file, and --coverlet-exclude-by-attribute; see its coverage options.

Microsoft code coverage settings

The Microsoft collector and dotnet-coverage can use XML or JSON settings. The XML example below uses ECMAScript regular expressions: Functions matches methods, Sources matches source files, and ModulePaths matches assemblies.

<Configuration>
  <CodeCoverage>
    <ModulePaths>
      <Exclude>
        <ModulePath>.*MyProduct\.Infrastructure\.dll</ModulePath>
      </Exclude>
    </ModulePaths>

    <Functions>
      <Exclude>
        <Function>^MyProduct\.Generated\..*</Function>
        <Function>^MyProduct\.Legacy\.LegacyAdapter\..*</Function>
      </Exclude>
    </Functions>

    <Sources>
      <Exclude>
        <Source>.*[\\/]Generated[\\/].*</Source>
      </Exclude>
    </Sources>
  </CodeCoverage>
</Configuration>

When an include list exists, a method must match it and must not match an exclude list. Built-in exclusions are merged by default; setting mergeDefaults="False" removes those defaults, so do so only when you intend to replace them. The configuration reference describes these semantics. Pass a settings file to dotnet-coverage with --settings, for example dotnet-coverage collect --settings coverage.settings.xml ...; see the command reference.

Rank #4

Fortnite Physical Gift Card

• An Epic Games account is required to redeem an Epic Games Store Card code
• If playing on a console platform (PlayStation Network, Xbox Live, Nintendo Switch or Mobile) you need to link your Epic Games account to that gaming platform (one time) to redeem your gift card code
• The 16 digit code on the back of the card WILL NOT work if redeemed directly through your gaming platform (PlayStation Network, Xbox Live, Nintendo Switch, Mobile, etc.)
• Note: Nintendo devices do not support Fortnite Shared Wallet, so V-Bucks purchased using your account balance will not show up on your Nintendo device. However, if you purchase items in the web Item Shop — or another platform where you play Fortnite — those items will be available in your Locker across all platforms.
• Redemption: Online

$50.00

Buy on Amazon

PHP with PHPUnit

PHPUnit defines the project source set in <source>. Its exclude entries remove files or directories from the source files used for coverage; they are not class-name filters. For example:

<source>
  <include>
    <directory suffix=".php">src</directory>
  </include>
  <exclude>
    <directory suffix=".php">src/Generated</directory>
    <file>src/Legacy/LegacyAdapter.php</file>
  </exclude>
</source>

includeUncoveredFiles="true" is the default: configured project files can count even if no line ran. Turning it off changes the denominator, so do not treat it as an exclusion-only cosmetic setting. PHPUnit’s UsesClass and related attributes describe code a test is allowed to use; they do not replace excluding a file from the project source set. For a genuinely untestable line or generated region, PHPUnit supports // @codeCoverageIgnore, @codeCoverageIgnoreStart, and @codeCoverageIgnoreEnd. See the XML configuration reference and code coverage manual.

JavaScript and TypeScript with NYC

NYC/Istanbul excludes files, not language-level classes, using minimatch globs. A custom exclude configuration replaces NYC’s defaults, so preserve any defaults you still need. This example deliberately lists its file policy:

{
  "nyc": {
    "all": true,
    "include": ["src/**/*.ts", "src/**/*.js"],
    "exclude": [
      "**/*.spec.ts",
      "**/*.test.ts",
      "src/generated/**",
      "src/legacy/LegacyAdapter.ts"
    ]
  }
}

NYC normally reports files visited during tests. Setting all: true adds unvisited eligible files, which can affect totals. Quote command-line globs so the shell does not expand them before NYC receives them. Keep compiled output and source-map handling consistent; otherwise a report may point to generated JavaScript instead of TypeScript. Istanbul pragmas such as /* istanbul ignore file */ and /* istanbul ignore next */ apply to files or code regions, not a substitute for a stable file policy. See the NYC documentation.

Best Value

$25 PlayStation Store Gift Card [Digital Code]

• Redeem for anything on PlayStationStore: games, add-ons, PlayStationPlus and more.
• Everything you want to play. Choose from the largest library of PlayStation content.
• Use gift card funds to contribute towards PlayStationPlus memberships.

$25.00

Buy on Amazon

Python with coverage.py

coverage.py filters files with --omit, [run] omit, or [report] omit; source-line exclusions use separate regular-expression rules. For example, a .coveragerc can define both measurement and reporting scope:

[run]
source = src
omit =
    src/generated/*
    src/legacy/legacy_adapter.py

[report]
omit =
    src/generated/*
    src/legacy/legacy_adapter.py

Or apply report-time filters to individual commands:

coverage report --omit='src/generated/*,src/legacy/legacy_adapter.py'
coverage html --omit='src/generated/*,src/legacy/legacy_adapter.py'

[run] omit affects measurement scope; [report] omit filters the output. With source configured, coverage.py can discover unexecuted files, so a file that never ran can still affect totals unless it is omitted. See the source selection documentation and exclusion rules.

C and C++ with gcovr

gcovr filters source paths rather than C++ classes. Its filters are regular expressions and use forward slashes even on Windows. For example:

gcovr \
  --root . \
  --filter 'src/' \
  --exclude 'src/generated/' \
  --exclude 'src/legacy/legacy_adapter\.cpp$' \
  --html-details coverage.html

If a class is split between a header and implementation, excluding only one file may leave coverage from the other. Header-only templates can appear through multiple translation units, so inspect the report after filtering. See the gcovr filter documentation.

Verify the resulting report and denominator

1. Find the producer and consumer. Record which command or build task creates the data, which command creates each report, and the exact XML, Cobertura, OpenCover, LCOV, or other artifact consumed by CI.
2. Apply the narrowest rule at the percentage stage. Prefer an exact type or file when one is intended; use package or directory patterns only when all matching code should be outside scope.
3. Regenerate from clean, current inputs. A stale class file, coverage data file, or report can make a correct-looking filter appear ineffective.
4. Inspect raw artifacts as well as HTML. Search for the class or source path in each report format used by a dashboard or gate. Check artifact path and timestamp in the pipeline if the displayed percentage seems inconsistent.
5. Compare counts, not just percentages. Review covered and total line, instruction, or branch counts before and after filtering. This shows whether the intended code left the denominator and whether unrelated code disappeared too.
6. Check aggregate reports and thresholds. Apply equivalent rules before merging inputs, or rebuild the aggregate from consistently filtered reports. Confirm the gate reads the filtered artifact, not a later unfiltered transformation.

Choose exclusions that preserve a useful metric

Excluding generated code, framework plumbing, adapters, or trivial data holders can make a product-code metric more useful. Excluding business logic just to raise a threshold makes the percentage less informative. When logic and boilerplate share a class, prefer excluding only generated members or lines if the tool supports it.

Document the reason for each exception, who owns it, and when it should be reviewed. Keep an unfiltered or audit report where practical. Coverage percentages are meaningful only alongside the scope used to calculate them; results with different inclusion rules are not directly comparable.

Quick Recap

Bestseller No. 1

GameStop Physical Gift Card

Over 6,100 stores located throughout the United States.; GameStop. Power to the Players.; Redemption: Instore and Online

$25.00

Bestseller No. 2

Xbox Physical Gift Card

MOVIES & TV SHOWS: Rent or buy new and popular movies and TV shows from a massive library.

$25.00

Bestseller No. 3

$100 XBOX Gift Card [Digital Code]

Gift cards are region‑specific (U.S. only) and cannot be transferred once redeemed.

$100.00

Bestseller No. 4

Fortnite Physical Gift Card

An Epic Games account is required to redeem an Epic Games Store Card code; Redemption: Online

$50.00

Bestseller No. 5

$25 PlayStation Store Gift Card [Digital Code]

Redeem for anything on PlayStationStore: games, add-ons, PlayStationPlus and more.; Everything you want to play. Choose from the largest library of PlayStation content.

$25.00

Troubleshoot common exclusion problems

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.