if you have a line of code that says var x= 10; console.log(x); that’s one line and 2 statements. Statement coverage has each statement in the program been executed. Line coverage has each executable line in the source file been executed.
Coverage is a subtle 😉 mix of the line and the branch coverage. You can find the formula on our metric description page: coverage = (CT + CF + LC)/(2*B + EL) where CT – branches that evaluated to “true” at least once CF – branches that evaluated to “false” at least once LC – … Read more
The solution was: [run] omit = ../*migrations*
One way to do it would be to put the functions you don’t want tested in a separate go file, and use a build tag to keep it from being included during tests. For example, I do this sometimes with applications where I have a main.go file with the main function, maybe a usage function, … Read more
The last release of ReportGenerator can merge cobertura files. You can install it from nuget usage: reportgenerator “-reports:target\*\*.xml” “-targetdir:C:\report” -reporttypes:Cobertura A file Corbertura.xml is generated in the targetdir directory You can use the dotnet core version to use it on linux or mac
I used the –no-external flag together with the –directory flag to exclude unwanted files. The definition of external from the man: External source files are files which are not located in one of the directories specified by –directory or –base-directory. So my command looked like this: $ lcov –directory src -c -o report.info –no-external Capturing … Read more
On the TypeScript team, we just use regular code coverage tools on the compiled JavaScript. We’ve found this to be more than sufficient, since usually for code coverage you are looking at total coverage % (which doesn’t change significantly) or are deep-diving at expression-level (which also doesn’t change significantly). If you found a tool that … Read more
I finally solved this problem by getting some help from the gcc guys. See the thread here: http://gcc.gnu.org/ml/gcc-help/2010-09/msg00130.html. It turns out that the .gcda files were being put in the .libs directory since that’s where the shared library (.so) files were. In order to get gcov to produce the output, I had to move the … Read more