code-coverage
Here are 192 public repositories matching this topic...
Hello! The documentation appears to indicate that Format can be specified on the command line for the VSTest integration (see https://github.com/tonerdo/coverlet/blob/master/Documentation/VSTestIntegration.md#coverlet-options-supported-by-vstest-integration), but it provides no examples on how to do so and I've had zero luck figuring it out myself. Assuming that is indeed possible, would someone b
-
Updated
May 17, 2020 - C#
-
Updated
May 17, 2020 - TypeScript
The README for nyc states:
Please start with the pre-configured @istanbuljs/nyc-config-babel preset [...]
The README for nyc-config-babel states:
Handy default configuration for instrumenting your babel-backed project [...]
When I configure my babel project without this package, everything seems to work correctly. None of the documentation I've found explains why I should pull in t
Is your feature request related to a problem? Please describe.
We have a database schema which includes temporary objects - this means objects which are required only for a short time like procedure for upgrades or objects which are still work in progress - and legacy test code. Temporary objects are always prefixed with the username of the author like:
windowsusr_my_table
Test Procedures a
If I understood the docs correctly, --disable-coverage-init is supposed to allow updating already existing coverage information with new test cases. However, I was unable to make it work, since it either complains that an existing cov directory was found or, if told to overwrite the directory with -O, it says /tmp/afl-ramdisk/out/cov/lcov/trace.lcov_info_final.
Could you add an example
Are there any instructions on how to use altcover.visualizer ?
I've installed it as a global dotnet tool, but typing altcover.visualizer at a cmd prompt doesn't do anything.
Should I be doing something else ?
When testing in a matrix, uploads often fail after the first one. I'm testing against different versions of Python, and I only need to upload the coverage information once, by including
if: matrix.python-version == 3.8in the codecov job. It took me a while to figure this out, so maybe it is nice to include this in the readme.
Example:
$pattern = "sign/in";
$actual = "https://test.dev/sign/in?_fid=j3o0";
\Tester\Assert::match($pattern, $actual);
Current tester output:
Failed: 'https://test.dev/sign/in?_fid=j3o0' should match
... 'sign/in' in testAbc()
It would nice something like:
Failed: 'wrong pattern format given.'
Failed: 'https://test.dev/sign/in?_fid=j3o0' should matc
-
Updated
Mar 24, 2020 - CMake
-
Updated
May 6, 2020 - C#
-
Updated
Feb 7, 2020 - Swift
In the README.md:
To get the best results, make sure that you have
coverage/.resultset.jsonin
your application directory. That wayskunkknows what's the status of your
test suite + code coverage.
Running skunk without that file is kind of pointless. The whole idea of the "StinkScore" is to combine RubyCritic's cost with SimpleCov's lack of coverage, in order to get a realistic "
-
Updated
Oct 30, 2019 - Ruby
-
Updated
May 13, 2020 - JavaScript
-
Updated
Apr 25, 2020 - CMake
-
Updated
Aug 29, 2017 - JavaScript
-
Updated
Feb 25, 2020 - Ruby
As asked in #52 the user wants to have spec file coverage in the report. Right now we strip this information, leaving code coverage for application source code only (see https://github.com/cypress-io/code-coverage/blob/master/support.js#L63). Make it into a configurable option.
The package name should be searchable by browser search function.
Right now you have to search by hand in a long unsorted list.
-
Updated
Feb 12, 2020 - PHP
-
Updated
May 30, 2019 - Java
-
Updated
May 4, 2020 - C++
-
Updated
May 16, 2020 - JavaScript
-
Updated
Mar 3, 2020 - PHP
-
Updated
Jan 23, 2019 - Python
Improve this page
Add a description, image, and links to the code-coverage topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the code-coverage topic, visit your repo's landing page and select "manage topics."
Just create
test.jswith content below and runnyc node test.jsNYC exits with an empty report: