code-coverage
Here are 202 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
Jun 6, 2020 - C#
-
Updated
Jun 22, 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
-
Updated
Jun 22, 2020 - CMake
-
Updated
Jun 22, 2020 - TypeScript
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
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.8
in the codecov job. It took me a while to figure this out, so maybe it is nice to include this in the readme.
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
Since dotnetcore's behavior when testing entire solution is trying also test non testing projects and then whole process is evaluated as non successful at least on linux, then I need to run test on one by one testing project separately I need to somehow then merge altcover results into one xml file, is that possible?
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
May 24, 2020 - CMake
-
Updated
Jun 13, 2020 - C#
-
Updated
Feb 7, 2020 - Swift
In the README.md:
To get the best results, make sure that you have
coverage/.resultset.json
in
your application directory. That wayskunk
knows 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
Jun 15, 2020 - JavaScript
-
Updated
Apr 25, 2020 - CMake
-
Updated
Oct 30, 2019 - 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.
-
Updated
Aug 29, 2017 - JavaScript
-
Updated
May 26, 2020 - Ruby
The package name should be searchable by browser search function.
Right now you have to search by hand in a long unsorted list.
-
Updated
May 30, 2019 - Java
-
Updated
Feb 12, 2020 - PHP
-
Updated
Jun 13, 2020 - JavaScript
-
Updated
May 4, 2020 - C++
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.js
with content below and runnyc node test.js
NYC exits with an empty report: