If you were to mandate a minimum percentage code-coverage for unit tests, perhaps even as a requirement for committing to a repository, what would it be?

Please explain how you arrived at your answer (since if all you did was pick a number, then I could have done that all by myself ;)

What is a reasonable code coverage % for unit tests (and why)?

After running coverage reports in Eclipse (using cobertura or an EMMA plugin), my source code files get highlighted in green, red and yellow depending on which lines of code were covered by tests.

How can I clear this highlighting after I&#39;m done?

Clearing coverage highlighting in Eclipse

I wonder what options there are for .NET (or C# specifically) code coverage, especially in the lower priced segment?

I am not looking for recommendations, but for a comparison of products based on facts. I know the following:

* [NCover][1]
  * Seems to be very popular and looks quite good
  * Supports statement coverage and branch coverage
  * [$480 for &quot;NCover 3 Complete&quot;][2]
  * Older beta versions are available [for free][3]
* [Visual Studio (2008 Pro) | (2005 Team System (Development, Test or Team Suite Editions))][4]
  * Well, it&#39;s Microsoft so I&#39;d expect it to work properly
  * Fully integrated into Visual Studio
  * At least $5,469
* [PartCover][6] - no further development (moved to OpenCover)
  * Open source
  * Supports statement coverage
* [OpenCover][7] - successor to PartCover
  * OpenSource
  * Supports branch and statement coverage
  * 32 and 64 bit support
  * Silverlight support
  * [Background][8]
  * [Tutorial on The Code Project by the primary developer][9]
  * No [.NET Core support yet][10]
* [SD Test Coverage][11]
  * Works with 32 and 64 bits, full C# 4.0
  * Handles both small and very large code bases
  * $250 for single user license
* [JetBrains dotCover][12]
  * $100 for Personal License. Free for user groups, open source projects, students and teachers.
  * Supports statement coverage
  * Silverlight support
* [NCrunch][13]
  * $159 for personal license
  * $289 for commercial seat license
&lt;s&gt;  * Free during beta, [to become commercial, pricing unknown][14] [future unknown][15]&lt;/s&gt;.
  * Code coverage indicators in Visual Studio
  * Continuous (near real time) testing
  * Visual per-test code coverage
  * Performance metrics, parallel multi-core test execution

* [NDepend][16]
  * [$410][17] for developer license
  * NDepend can import coverage data from NCover, DotCover, Visual Studio 2017; 2015, 2013, 2012, 2010 and 2008 Code Coverage files.
  * Dependency graph
  * Dependency structure matrix
  * Visualizing code metrics
  * Validating code rules

  [1]: http://www.ncover.com/
  [2]: https://www.ncover.com/quote
  [3]: https://stackoverflow.com/questions/276829/code-coverage-for-cnet#276840
  [4]: https://web.archive.org/web/20090118182937/http://msdn.microsoft.com/en-us/vstudio/products/cc149003.aspx
  [5]: http://msdn.microsoft.com/en-us/vsts2008/products/cc263908.aspx
  [6]: https://github.com/sawilde/partcover.net4
  [7]: https://github.com/OpenCover/opencover
  [8]: http://scubamunki.blogspot.com/2011/06/opencover-first-beta-release.html
  [9]: https://www.codeproject.com/Articles/677691/Getting-code-coverage-from-your-NET-testing-using
  [10]: https://github.com/OpenCover/opencover/issues/595
  [11]: http://www.semanticdesigns.com/Products/TestCoverage/CSharpTestCoverage.html
  [12]: https://www.jetbrains.com/dotcover/
  [13]: https://www.ncrunch.net/
  [14]: https://blog.ncrunch.net/post/The-Future-Of-NCrunch-Part-2.aspx
  [15]: https://blog.ncrunch.net/post/The-Future-of-NCrunch.aspx
  [16]: https://www.ndepend.com/Coverage.aspx
  [17]: https://www.ndepend.com/Purchase.aspx




What can I use for good quality code coverage for C#/.NET?

I am using Mocha for testing my NodeJS application. I am not able to figure out how to use its code coverage feature. I tried googling it but did not find any proper tutorial. Please help.

Code coverage with Mocha

What is code coverage and how do YOU measure it?

I was asked this question regarding our automating testing code coverage. It seems to be that, outside of automated tools, it is more art than science. Are there any real-world examples of how to use code coverage?


What is code coverage and how do YOU measure it?

# Problem:

I have a project with [tag:JaCoCo] and I want to be able to filter certain classes and/or packages.

# Related Documentation:

I have read the following documentation:

**Official [tag:JaCoCo] site:**
http://www.eclemma.org/jacoco/index.html

**Official [tag:JaCoCo] docs for [tag:Gradle]:** https://gradle.org/docs/current/userguide/jacoco_plugin.html

**Official [tag:JaCoCo] `Github` issues, working on coverage:**
https://github.com/jacoco/jacoco/wiki/FilteringOptions
https://github.com/jacoco/jacoco/issues/14

# Related StackOverflow Links:
https://stackoverflow.com/questions/19625640/jacoco-gradle-filtering-options (No answer)

https://stackoverflow.com/questions/27033757/exclude-packages-from-jacoco-report-using-sonarrunner-and-gradle (Not using [tag:sonar])

https://stackoverflow.com/questions/14682389/jacoco-exclude-jsp-from-report (It seems to work for [tag:maven], I am using [tag:gradle])

https://stackoverflow.com/questions/27799419/maven-jacoco-configuration-exclude-classes-packages-from-report-not-working (It seems to work for [tag:maven], I am using [tag:gradle])

https://stackoverflow.com/questions/23756014/jacoco-gradle-plugin-exclude (Could not get this to work)

https://stackoverflow.com/questions/17394427/gradle-jacoco-coverage-reports-includes-classes-excluded-in-configuration (Seems very close, it used `doFirst`, did not work for me)

# Example of what I have tried:

    apply plugin: &#39;java&#39;
    apply plugin: &#39;jacoco&#39;
    
    buildscript {
        repositories {
            mavenCentral()
            jcenter()
        }
    }
    
    repositories {
        jcenter()
    }
    
    jacocoTestReport {
        reports {
            xml {
                enabled true // coveralls plugin depends on xml format report
            }
    
            html {
                enabled true
            }
        }

        test {
            jacoco {
                destinationFile = file(&quot;$buildDir/jacoco/jacocoTest.exec&quot;)
                classDumpFile = file(&quot;$buildDir/jacoco/classpathdumps&quot;)
                excludes = [&quot;projecteuler/**&quot;] // &lt;-- does not work
                // excludes = [&quot;projecteuler&quot;]
            }
        }
    }

# Question:
**How can I exclude certain packages and classes when generating the [tag:JaCoCo] coverage reports?**

Filter JaCoCo coverage reports with Gradle

I&#39;m using [ember-cli-code-coverage][1] with [ember-cli-mocha][2]. When I run `COVERAGE=true ember test` I&#39;m getting 0% coverage for statements, functions, and lines. Yet, I have tests that are covering those sections. Any I missing something in my setup?



[![enter image description here][3]][3]

unit test file:

      beforeEach(function() {
        controller = this.subject();
      });
    
      it(&#39;sets selectedImage to null&#39;, function() {
        expect(controller.get(&#39;selectedImage&#39;)).to.eql(null);
      });
    
      describe(&#39;setCoverageTest&#39;, function() {
        it(&#39;sets selectedImage to true&#39;, function()  {
          expect(controller.get(&#39;selectedImage&#39;)).to.eql(null);
          controller.setCoverageTest();
          expect(controller.get(&#39;selectedImage&#39;)).to.be.true;
        });
      });
    

config/coverage.js:

    module.exports = {
      excludes: [&#39;*/templates/**/*&#39;],
      useBabelInstrumenter: true
    };


  [1]: https://github.com/kategengler/ember-cli-code-coverage
  [2]: https://github.com/ember-cli/ember-cli-mocha
  [3]: https://i.stack.imgur.com/Oc9Yz.png

ember-cli-code-coverage mocha showing 0% coverage when there are tests

Has anyone succeeded in generating code coverage for Go unit tests? I can&#39;t find a tool for that on the web.

How to measure test coverage in Go

The calculations in my code are well-tested, but because there is so much GUI code, my overall code coverage is lower than I&#39;d like. Are there any guidelines on unit-testing GUI code? Does it even make sense?

For example, there are graphs in my app. I haven&#39;t been able to figure out how to automate the testing of the graphs. It takes a human eye, AFAIK, to check if the graph is correct.

(I&#39;m using Java Swing)


How can I unit test a GUI?

I&#39;ve searched up and down the internet for this one. There&#39;s lots of half-answers out there, to do with Maven properties such as `${sonar.jacoco.reportPath}`, or `org.jacoco:jacoco-maven-plugin:prepare-agent` or setting `maven-surefire-plugin` `argLine` with `-javaagent`.

Some how, none of these answers, either on their own, or in combination, are producing what I&#39;m after:
A coverage report which shows a class as covered if it is used in tests higher up the stack, such as entities being used by DAOs, even though it was not fully covered by tests in its own module.

Is there a definitive config somewhere, to achieve this, please?


How to configure multi-module Maven + Sonar + JaCoCo to give merged coverage report?

I&#39;ve always used Jasmine for my unit tests, but recently I started using Istanbul to give me code coverage reports. I mean I get the *gist* of what they are trying to tell me, but I don&#39;t really know what each of these percentages represent (Stmts, Branches, Funcs, Lines). So far Googling I have been unable to find a solid explanation/resource. 

**Question**: Like I said I get the gist of it, but can someone post either a proper explanation or a link to a proper explanation?

**Tertiary Question**: Is there any way to identify what specific parts of your code aren&#39;t covered? So far without really grokking this report I&#39;m basically guessing.

    -------------------|-----------|-----------|-----------|-----------|
    File               |   % Stmts |% Branches |   % Funcs |   % Lines |
    -------------------|-----------|-----------|-----------|-----------|
       controllers/    |      88.1 |     77.78 |     78.57 |      88.1 |
          dashboard.js |      88.1 |     77.78 |     78.57 |      88.1 |
    -------------------|-----------|-----------|-----------|-----------|
    All files          |      88.1 |     77.78 |     78.57 |      88.1 |
    -------------------|-----------|-----------|-----------|-----------|

How do I read an Istanbul Coverage Report?

I have configured IntelliJ to paint the background of any line that has been executed at runtime to green when running in Coverage mode.

At times, I would like to just make all the files in the project revert back to their old and typical background colors, i.e, to remove all the coverage information. 

Is that possible? How?


Clear code coverage information in IntelliJ

This is the code:

    package com.XXX;
    public final class Foo {
      private Foo() {
        // intentionally empty
      }
      public static int bar() {
        return 1;
      }
    }

This is the test:

    package com.XXX;
    public FooTest {
      @Test 
      void testValidatesThatBarWorks() {
        int result = Foo.bar();
        assertEquals(1, result);
      }
      @Test(expected = java.lang.IllegalAccessException.class)
      void testValidatesThatClassFooIsNotInstantiable() {
        Class cls = Class.forName(&quot;com.XXX.Foo&quot;);
        cls.newInstance(); // exception here
      }
    }

Works fine, the class is tested. But Cobertura says that there is zero code coverage of the private constructor of the class. How can we add test coverage to such a private constructor?

How to add test coverage to a private constructor?

What code analysis tools do you use on your Java projects?

I am interested in all kinds

- static code analysis tools (FindBugs, PMD, and any others)
- code coverage tools (Cobertura, Emma, and any others)
- any other instrumentation-based tools 
- anything else, if I&#39;m missing something

If applicable, also state what build tools you use and how well these tools integrate with both your IDEs and build tools. 

If a tool is only available a specific way (as an IDE plugin, or, say, a build tool plugin) that information is also worth noting.

What code analysis tools do you use for your Java projects?

Since NCrunch has left the free market, I was looking for a similar tool for code coverage marking, and continous testing like NCrunch

edit: I&#39;m using VS2012

update: 

I&#39;ve been using ContinuousTest for a while now, it&#39;s OK, but I think it lacks feedback when I write code. The feedback is good when I write tests, but when I break a test (while editing source code) it won&#39;t tell me that the test broke (in the margin, like it does for NCrunch). So if anyone knows other tools, I&#39;m still listening.

Free NCrunch alternative

I&#39;m kind of a rookie with python unit testing, and particularly coverage.py.  Is it desirable to have coverage reports include the coverage of your actual test files?

Here&#39;s a screenshot of my [HTML report][1] as an example.

You can see that the report includes `tests/test_credit_card`.  At first I was trying to omit the `tests/` directory from the reports, like so:

    coverage html --omit=tests/ -d tests/coverage

I tried several variations of that command but I could *not* for the life of me get the tests/ excluded.  After accepting defeat, I began to wonder if maybe the test files are *supposed* to be included in the report.

Can anyone shed some light on this?  

  [1]: http://kylefox-awesome-stuff.s3.amazonaws.com/coverage.png

Is it possible exclude test directories from coverage.py reports?

I generated a code coverage report from jacoco, which is *jacoco.exec*. But I don&#39;t know how to use it ...

The way I generated it is through command line:

    java -javaagent:/path/to/jacocoagent.jar=include=some.package.*,output=file org.junit.runner.JUnitCore some.package.ClassTest


Then I got the jacoco.exec report. All I need is just the number of percentage, and I am using command line only. Is there a way to convert this report to a readable txt file?

Thanks all

how to use jacoco.exec report

Most Stackoverflow answers that I have found in regards to the Perl build process and unit testing and code coverage simply point me to CPAN for the documentation there.  There&#39;s absolutely nothing wrong with pointing to CPAN modules because that&#39;s where the full documentation is supposed to reside.  I&#39;ve had trouble finding complete working code examples in many cases, though.  

I&#39;ve been searching all over the Internet for actual working code samples that I can download or paste into my IDE, like your typical tutorial &quot;Hello World&quot; example source code, but of an example that demonstrates the build process with unit testing and code coverage analysis.  Does anyone have a small example of a complete working project that demonstrates these technologies and processes?  

*(I do have a small working example and I will answer my own question with it, but there are probably other SO users who have better examples than the ones I came up with.)*


Perl build, unit testing, code coverage: A complete working example

I have an *enum* switch more or less like this:

    public static enum MyEnum {A, B}

    public int foo(MyEnum value) {
        switch(value) {
            case(A): return calculateSomething();
            case(B): return calculateSomethingElse();
        }
        throw new IllegalArgumentException(&quot;Do not know how to handle &quot; + value);
    }

and I&#39;d like to have all the lines covered by the tests, but as the code is expected to deal with all possibilities, I cannot supply a value without its corresponding case statement in the switch.

Extending the enum to add an extra value is not possible, and just mocking the equals method to return `false` won&#39;t work either because the bytecode generated uses a jump table behind the curtains to go to the proper case... So I&#39;ve thought that maybe some black magic could be achieved with PowerMock or something.

Thanks!

**edit**:

As I own the enumeration, I&#39;ve thought that I could just add a method to the values and thus avoid the switch issue completely; but I&#39;m leaving the question as it&#39;s still interesting.

Mocking Java enum to add a value to test fail case

I would like to use PHPUnit to create code coverage reports. I have tried a lot of installation setups found on the web. But nothing seems to work out.

I use the latest version of Laravel 5 (&gt;5.2) and PHPUnit v. 5.0.10. Further, I use MAMP on Mac OS X 10.9.5 running PHP 7. 

When I run PHPUnit that is integrated in my Laravel distribution, I receive the following error.

    $ vendor/bin/phpunit -v
    PHPUnit 5.0.10 by Sebastian Bergmann and contributors.

    Runtime:       PHP 7.0.0
    Configuration: /Applications/MAMP/htdocs/myProject/phpunit.xml
    Error:         No code coverage driver is available`

My composer file looks like:


	&quot;require-dev&quot;: {
	    &quot;fzaninotto/faker&quot;: &quot;~1.4&quot;,
	    &quot;mockery/mockery&quot;: &quot;0.9.*&quot;,
	    &quot;phpunit/phpunit&quot;: &quot;5.0.*&quot;,
	    &quot;phpunit/php-code-coverage&quot;: &quot;^3&quot;,
	    &quot;symfony/css-selector&quot;: &quot;2.8.*|3.0.*&quot;,
	    &quot;symfony/dom-crawler&quot;: &quot;2.8.*|3.0.*&quot;
	},

I have also tried the following command:

    /Applications/MAMP/bin/php/php7.0.0/bin/phpdbg -qrr ../../../htdocs/myProject/vendor/bin/phpunit -v

This seems to set up the code coverage driver well, but it ends up in an exception:


	$ /Applications/MAMP/bin/php/php7.0.0/bin/phpdbg -qrr ../../../htdocs/myProject/vendor/bin/phpunit -v
	PHPUnit 5.0.10 by Sebastian Bergmann and contributors.

	Runtime:       PHPDBG 7.0.0
	Configuration: /Applications/MAMP/htdocs/myProject/phpunit.xml

	[PHP Fatal error:  Uncaught ErrorException: include(/Applications/MAMP/htdocs/myProject/app/Exceptions/Handler.php): failed to open stream: Too many open files in /Applications/MAMP/htdocs/myProject/vendor/composer/ClassLoader.php:412
	Stack trace:
	...

The phpunit.xml looks as follows:

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
    &lt;phpunit backupGlobals=&quot;false&quot;
         backupStaticAttributes=&quot;false&quot;
         bootstrap=&quot;bootstrap/autoload.php&quot;
         colors=&quot;true&quot;
         convertErrorsToExceptions=&quot;true&quot;
         convertNoticesToExceptions=&quot;true&quot;
         convertWarningsToExceptions=&quot;true&quot;
         processIsolation=&quot;false&quot;
         stopOnFailure=&quot;false&quot;&gt;
        &lt;testsuites&gt;
            &lt;testsuite name=&quot;Application Test Suite&quot;&gt;
                &lt;directory&gt;./tests/&lt;/directory&gt;
            &lt;/testsuite&gt;
        &lt;/testsuites&gt;
        &lt;logging&gt;
          &lt;log type=&quot;coverage-html&quot; target=&quot;./tests/codeCoverage&quot; charset=&quot;UTF-8&quot;/&gt;
        &lt;/logging&gt;
        &lt;filter&gt;
            &lt;whitelist&gt;
                &lt;directory suffix=&quot;.php&quot;&gt;app/&lt;/directory&gt;
            &lt;/whitelist&gt;
        &lt;/filter&gt;
        &lt;php&gt;
            &lt;env name=&quot;APP_ENV&quot; value=&quot;testing&quot;/&gt;
            &lt;env name=&quot;CACHE_DRIVER&quot; value=&quot;array&quot;/&gt;
            &lt;env name=&quot;SESSION_DRIVER&quot; value=&quot;array&quot;/&gt;
            &lt;env name=&quot;QUEUE_DRIVER&quot; value=&quot;sync&quot;/&gt;
        &lt;/php&gt;
    &lt;/phpunit&gt;


Is it possible to use PHPUnit that comes with the Laravel framework together with code coverage? How should I set it up and use it?

Thanks a lot for your help.

Laravel 5: PHPUnit and no code coverage driver available

I use [Istanbul][1] for code coverage of unit tests in an AngularJS project. There are 4 types of coverage and they are

 - statement
 - branch
 - function
 - line

Statement, function and line are alright but i don&#39;t understand what &quot;branch&quot; is. What is branch?


  [1]: https://gotwarlost.github.io/istanbul/

What is a branch in code coverage for JavaScript unit testing

I am developing apps using Android Studio.&lt;br/&gt;
I was able to run the test code.&lt;br/&gt;
But, I do not know how to get code coverage in android studio.

**I have already seen the following links.**&lt;br/&gt;
https://stackoverflow.com/questions/17100830/android-gradle-code-coverage&lt;br/&gt;
But I can&#39;t wait for update to v0.6 supporting emma.

**Project configuration is as follows.**&lt;br/&gt;

**Main code**&lt;br/&gt; 
MyProject/AppName/src/main/java/mypackage/MyClass.java

**Test code**&lt;br/&gt;
MyProject/AppName/src/instrumentTest/java/mypackage/test/MyClassTest.java

**Project configuration**&lt;br/&gt;
MyProject&lt;br/&gt;
├─build.gradle&lt;br/&gt;
└─AppName&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;├─build.gradle&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;└─src&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;├─main&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;│&amp;nbsp;&amp;nbsp;├─java&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;│&amp;nbsp;&amp;nbsp;│&amp;nbsp;&amp;nbsp;└─mypackage&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;│&amp;nbsp;&amp;nbsp;│&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;└─MyClass.java&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;│&amp;nbsp;&amp;nbsp;├─res&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;│&amp;nbsp;&amp;nbsp;└─AndroidManifest.xml&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;└─instrumentTest&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;└─java&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;└─mypackage&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;└─test&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;└─MyClassTest.java&lt;br/&gt;


How to get code coverage using Android Studio?

I&#39;m working on a Flutter app using Android Studio as my IDE. I&#39;m attempting to write tests and check the code coverage but I can&#39;t work out how to view the data in the IDE or any other application.  

By running `flutter test --coverage`, a coverage report seems to be generated into a file `/coverage/lcov.info`. That file looks something like this:

```lcov
SF:lib\data\Customer.g.dart
DA:9,2
DA:10,2
DA:11,2
DA:12,2
DA:13,2
DA:20,0
DA:21,0
DA:22,0
DA:23,0
DA:24,0
...
```

Looking at the file it seems to have a list of my project files with line by line coverage data. Is there a way to view this information in Android Studio?

How can the code coverage data from Flutter tests be displayed?

How do I find what code is and isn&#39;t being run **in production** ? 

The app is well-tested, but there&#39;s a lot of tests that test *unused* code. Hence they get coverage when running tests... I&#39;d like to refactor and clean up this mess, it keeps wasting my time. 
I have a lot of background jobs, this is why I&#39;d like the production env to guide me. Running at heroku I can spin up dynos to compensate any performance impacts from the profiler.

Related question https://stackoverflow.com/q/2958443/252799 not helpful. 

Bonus: metrics to show how often a line of code is run. Don&#39;t know why I want it, but I do! :)

Find unused code in a Rails app

Is there a way to see the code coverage when using nUnit? I know there&#39;s such a feature in Visual Studio, but can you use it with nUnit or only with the built-in vs unit tests?

Code coverage with nUnit?

How do code coverage tools like NCover know what parts of the code were executed and what parts were not?

How do code coverage tools work?

I&#39;ve got some code that uses try with resources and in jacoco it&#39;s coming up as only half covered. All the source code lines are green, but I get a little yellow symbol telling me that only 4 of 8 branches are covered.

![enter image description here][1]

I&#39;m having trouble figuring out what all the branches are, and how to write code that covers them. Three possible places throw `PipelineException`. These are `createStageList()`, `processItem()` and the implied `close()`

 1. Not throwing any exceptions, 
 1. throwing an exception from `createStageList()`
 1. throwing an exception from `processItem()`
 1. throwing an exception from `close()`
 1. throwing an exception from `processItem()` and `close()`

I can&#39;t think of any other cases, yet I still only have 4 of 8 covered.

Can someone explain to me why it&#39;s 4 of 8 and is there anyway to hit all 8 branches? I&#39;m not skilled with decyrpting/reading/interpreting byte code, but maybe you are... :) I&#39;ve already seen https://github.com/jacoco/jacoco/issues/82, but neither it nor the issue it references help very much (other than noting that this is due to compiler generated blocks)

Hmm, just as I finish writing this I had a thought on what case(s) might not be not tested by what I mention above... I&#39;ll post an answer if I got it right. I&#39;m sure this question and it&#39;s answer will help someone in any case.

**EDIT:** Nope, I didn&#39;t find it. Throwing RuntimeExceptions (not handled by the catch block) didn&#39;t cover any more branches

  [1]: http://i.stack.imgur.com/SggR6.png

8 branches for try with resources - jacoco coverage possible?

I am new to coverage and ran into a strange problem. My coverage is taking my virtual environment site packages into account.
Here is the output of the coverage run:

    coverage run test.py
    ....................
    ----------------------------------------------------------------------
    Ran 20 tests in 0.060s
    
    OK
    (atcatalog)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -jmfrank63@fullstack-audio-text-catalog:~/workspace (git master)       [19:58:45]
    $ coverage report
    Name                                                                              Stmts   Miss  Cover
    -----------------------------------------------------------------------------------------------------
    /home/ubuntu/Envs/atcatalog/lib/python2.7/site-packages/flask/__init__               18      0   100%
    /home/ubuntu/Envs/atcatalog/lib/python2.7/site-packages/flask/_compat                38     20    47%
    /home/ubuntu/Envs/atcatalog/lib/python2.7/site-packages/flask/app                   528    255    52%
    /home/ubuntu/Envs/atcatalog/lib/python2.7/site-packages/flask/blueprints            156    118    24%
                                 .
                                 .
                                 .
    /home/ubuntu/Envs/atcatalog/lib/python2.7/site-packages/werkzeug/urls               412    215    48%
    /home/ubuntu/Envs/atcatalog/lib/python2.7/site-packages/werkzeug/utils              242    175    28%
    /home/ubuntu/Envs/atcatalog/lib/python2.7/site-packages/werkzeug/wrappers           568    298    48%
    /home/ubuntu/Envs/atcatalog/lib/python2.7/site-packages/werkzeug/wsgi               448    352    21%
    atcatalog/__init__                                                                    7      0   100%
    atcatalog/views/__init__                                                              0      0   100%
    atcatalog/views/publang                                                               7      0   100%
    atcatalog/views/pubtext                                                               1      0   100%
    atcatalog/views/userlang                                                             13      0   100%
    atcatalog/views/users                                                                 5      0   100%
    atcatalog/views/usertext                                                             14      0   100%
    test                                                                                120      0   100%
    -----------------------------------------------------------------------------------------------------
    TOTAL                                                                             12530   8044    36%
    (atcatalog)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -jmfrank63@fullstack-audio-text-catalog:~/workspace (git master)       [19:58:55]

Here is the structure of my project directory which resides under home:

    workspace/
    ├── README.md
    ├── atcatalog
    │&#160;&#160; ├── __init__.py
    │&#160;&#160; ├── __init__.pyc
    │&#160;&#160; ├── static
    │&#160;&#160; ├── templates
    │&#160;&#160; └── views
    │&#160;&#160;     ├── __init__.py
    │&#160;&#160;     ├── __init__.pyc
    │&#160;&#160;     ├── publang.py
    │&#160;&#160;     ├── publang.pyc
    │&#160;&#160;     ├── pubtext.py
    │&#160;&#160;     ├── pubtext.pyc
    │&#160;&#160;     ├── userlang.py
    │&#160;&#160;     ├── userlang.pyc
    │&#160;&#160;     ├── users.py
    │&#160;&#160;     ├── users.pyc
    │&#160;&#160;     ├── usertext.py
    │&#160;&#160;     └── usertext.pyc
    ├── requirements.txt
    ├── run.py
    └── test.py


I had the virtual environment at first inside the project directory and now moved it out to ~/Envs with virtualenvwrapper, but the problem persisted.
run.py and test.py are not special in any way, they both import app from atcatalog.
I also tried to find ways to omit the virtual environment directory, but google gave no answer (surprisingly).
I don&#39;t think it is the purpose of coverage to test already well tested site-packages. So I would exclude them from the run.

How can I accomplish to avoid coverage having testing my site-packages?



preventing python coverage from including virtual environment site packages

I have a [Heaviside step function][1] centered on unity for any data type, which I&#39;ve encoded using:

    template &lt;typename T&gt;
    int h1(const T&amp; t){
       if (t &lt; 1){
           return 0;
       } else if (t &gt;= 1){
           return 1;
       }
    }

In code review, my reviewer told me that there is not an explicit return on all control paths. And the compiler does not warn me either. But I don&#39;t agree; the conditions are mutually exclusive. How do I deal with this?

  [1]: https://en.wikipedia.org/wiki/Heaviside_step_function


Does this function have explicit return values on all control paths?

I&#39;m using CMake with my project and set up a cdash server for continuous/nightly building. Everything works well and by setting up a crontab, we have hourly/nightly build/test results uploaded to our cdash server automatically.

My next step is to add test coverage report to the build. I find the document here http://www.cmake.org/Wiki/CTest:Coverage but frankly it&#39;s a bit far from a practical guide.

Currently I&#39;ve added the required flag (instead of `-fprofile-arcs -ftest-coverage`, I find `--coverage` better), the compilation process generates .gcno files. But then I&#39;m stuck. The command 

    make NightlyCoverage

doesn&#39;t seem to do anything. Could anybody tell me what is the next to do? The result that I want, is by doing `make NightlyCoverage`, coverage reports are generated and uploaded to cdash server.



Detailed guide on using gcov with CMake/CDash?

I&#39;m using gcov to measure coverage in my C++ code.  I&#39;d like to get to 100% coverage, but am hampered by the fact that there are some lines of code that are theoretically un-hittable (methods that are required to be implemented but which are never called, default branches of `switch` statements, etc.).  Each of these branches contains an `assert( false );` statement, but gcov still marks them as un-hit.

I&#39;d like to be able to tell gcov to ignore these branches.  Is there any way to give gcov that information -- by annotating the source code, or by any other mechanism?


How do I tell gcov to ignore un-hittable lines of C++ code?

In Jest, is there any way to ignore code for test coverage? 
I tried using 
```javascript
/* istanbul ignore next */
```
But it doesn&#39;t seem to work.

How to ignore lines for code coverage in Jest

I&#39;ve got an existing C# 4 project which I&#39;ve checked the test coverage for by using TestDriven.Net and the Visual Studio coverage feature, i.e. Test With -&gt; Coverage from the context menu.

The project contains some code I don&#39;t want covered, and I&#39;ve solved that by adding the `[ExcludeFromCodeCoverage]` for those types and methods.

We&#39;ve just upgraded TeamCity to 6.0.3, and I&#39;ve added dotCover coverage to the NUnit build step.

I&#39;ve managed to remove coverage for external assemblies such as NHibernate in the &quot;Filters&quot; section (by explicitly state the assemblies for which I want coverage), but I&#39;m struggling with how to exclude types and methods from covered assemblies.

![enter image description here][1]


  [1]: http://i.stack.imgur.com/Q4iNJ.png

How do I exclude types and methods from being covered by dotCover in TeamCity?

Is there a way to exclude code from inclusion into Cobertura coverage reports? We have some methods that should not be included in the coverage report and therefore not drive down the coverage numbers.

I know that Clover has such a functionality, but I have not found anything similar for Cobertura.

Exclude methods from code coverage with Cobertura

I have switched to the newest JDK 7 and I am having problems with running testng unit test on byte code that is fiddled by emma coverage tool. None of my test cases are run correctly and for most of them I am receiving such errors.

     java.lang.ClassFormatError: Illegal local variable table length 10 in method measurement.meter.AbstractSerialPortMeter.&lt;init&gt;(Lmeasurement/meter/SerialPort;)V at measurement.meter.Elc3133aTest.setUp(Elc3133aTest.java:42)

I have found an article here [JSR 292 Goodness Fast Code Coverage Tool Less 10k][1],
which is saying that &quot;JSR 292 introduces a new bytecode instruction invokedynamic but also several new kind of constant pool constants. Which means that most of the tools that parse bytecodes like ASM, BCEL, findbugs or EMMA will need to be updated to be java 7 compatible.&quot;

Checked Emma homepage, but it looks like it has not been updated for a long long time.

Has anybody solved a similar problem?

I have also tried with Cobertura. It looks to work a bit better but I am getting a lot of exceptions of type `VerifyError`.

    java.lang.VerifyError: Expecting a stackmap frame at branch target 85 in method measurement.meter.AbstractSerialPortMeter.close()V at offset 26
	at measurement.meter.AbstractSerialPortMeterTest.setUp(AbstractSerialPortMeterTest.java:27)



  [1]: http://weblogs.java.net/blog/forax/archive/2011/02/12/jsr-292-goodness-fast-code-coverage-tool-less-10k

Testng, Emma, Cobertura, coverage and JDK 7 result in ClassFormatError and VerifyError

I search a code coverage plugin for eclipse.
My question is simple:

Which plugin do you use with eclipse for code coverage and why ?

Eclipse plugin for code coverage

I have some code in Java that I want to exclude from code coverage. How would I do this? I want to be able to add an annotation. Is there a way to configure or extend jacoco (as used in gradle) to use this?

Example:

    public class Something
    {
        @ExcludeFromCodeCoverage
        public void someMethod() {}
    }

How would I add an annotation to exclude a method from a jacoco code coverage report?

Given software where ...

- The system consists of a few subsystems
- Each subsystem consists of a few components
- Each component is implemented using many classes

... I like to write automated tests of each subsystem or component.

I don&#39;t write a test for each internal class of a component (except inasmuch as each class contributes to the component&#39;s public functionality and is therefore testable/tested from outside via the component&#39;s public API).

When I refactor the implementation of a component (which I often do, as part of adding new functionality), I therefore don&#39;t need to alter any existing automated tests: because the tests only depend on the component&#39;s public API, and the public APIs are typically being expanded rather than altered.

I think this policy contrasts with a document like [Refactoring Test Code][1], which says things like ...

- &quot;... unit testing ...&quot;
- &quot;... a test class for every class in the system ...&quot;
- &quot;... test code / production code ratio ... is ideally considered to approach a ratio of 1:1 ...&quot;

... all of which I suppose I disagree with (or at least don&#39;t practice).

**My question is, if you disagree with my policy, would you explain why? In what scenarios is this degree of testing insufficient?**

In summary:

- Public interfaces are tested (and retested), and rarely change (they&#39;re added to but rarely altered)
- Internal APIs are hidden behind the public APIs, and can be changed without rewriting the test cases which test the public APIs

---

Footnote: some of my &#39;test cases&#39; are actually implemented as data. For example, test cases for the UI consist of data files which contain various user inputs and the corresponding expected system outputs. Testing the system means having test code which reads each data file, replays the input into the system, and asserts that it gets the corresponding expected output.

Although I rarely need to change test code (because public APIs are usually added to rather than changed), I do find that I sometimes (e.g. twice a week) need to change some existing data files. This can happens when I change the system output for the better (i.e. new functionality improves existing output), which might cause an existing test to &#39;fail&#39; (because the test code only tries to assert that output hasn&#39;t changed). To handle these cases I do the following:

- Rerun the automated test suite which a special run-time flag, which tells it to not assert the output, but instead to capture the new output into a new directory
- Use a visual diff tool to see which output data files (i.e. what test cases) have changed, and to verify that these changes are good and as expected given the new functionality
- Update the existing tests by copying new output files from the new directory into the directory from which test cases are run (over-writing the old tests)

---

Footnote: by &quot;component&quot;, I mean something like &quot;one DLL&quot; or &quot;one assembly&quot; ... something that&#39;s big enough to be visible on an architecture or a deployment diagram of the system, often implemented using dozens or 100 classes, and with a public API that consists of only about 1 or a handful of interfaces ... something that may be assigned to one team of developers (where a different component is assigned to a different team), and which will therefore according to [Conway&#39;s Law][2] having a relatively stable public API.

---

Footnote: The article _[Object-Oriented Testing: Myth and Reality][3]_ says,

&gt; **Myth: Black box testing is sufficient.**
&gt; If you do a careful job of test case
&gt; design using the class interface or
&gt; specification, you can be assured that
&gt; the class has been fully exercised.
&gt; White-box testing (looking at a
&gt; method&#39;s implementation to design
&gt; tests) violates the very concept of
&gt; encapsulation. 
&gt; 
&gt; **Reality: OO structure matters, part
&gt; II.** Many studies have shown that
&gt; black-box test suites thought to be
&gt; excruciatingly thorough by developers
&gt; only exercise from one-third to a half
&gt; of the statements (let alone paths or
&gt; states) in the implementation under
&gt; test. There are three reasons for
&gt; this. First, the inputs or states
&gt; selected typically exercise normal
&gt; paths, but don&#39;t force all possible
&gt; paths/states. Second, black-box
&gt; testing alone cannot reveal surprises.
&gt; Suppose we&#39;ve tested all of the
&gt; specified behaviors of the system
&gt; under test. To be confident there are
&gt; no unspecified behaviors we need to
&gt; know if any parts of the system have
&gt; not been exercised by the black-box
&gt; test suite. The only way this
&gt; information can be obtained is by code
&gt; instrumentation. Third, it is often
&gt; difficult to exercise exception and
&gt; error-handling without examination of
&gt; the source code.

I should add that I&#39;m doing whitebox functional testing: I see the code (in the implementation) and I write functional tests (which drive the public API) to exercise the various code branches (details of the feature&#39;s implementation).


  [1]: http://www.agilealliance.org/system/article/file/995/file.pdf
  [2]: http://en.wikipedia.org/wiki/Conway&#39;s_Law
  [3]: http://www.rbsc.com/pages/myths.html

Should one test internal implementation, or only test public behaviour?

What are the available code coverage tools for Scala? 

I have Scala spec tests and a Hudson continuous integration set-up. Is there something I can hook-in to this setup to measure and track code coverage?


Code Coverage Tools for Scala

Do your unit tests constitute 100% code coverage? Yes or no, and why or why not.

Unit testing code coverage - do you have 100% coverage?

How do I exclude entire files from [coverage.py][1] reports?

According to the documentation you can exclude code by matching lines. I want to exclude entire files, so that the reports don&#39;t include 3rd party libraries. Am I missing something? Can it be done?


  [1]: http://nedbatchelder.com/code/coverage/

All Code Coverage Solutions on Gang of Coders

Total of 41 Code Coverage Solutions