Skip to content
#

code-coverage

Here are 202 public repositories matching this topic...

xuld
xuld commented Feb 15, 2020

Just create test.js with content below and run nyc node test.js

var await;

NYC exits with an empty report:

 ----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
----------|---------|----------|---------|---------|-------------------
All files |       0 |        0 |       0 |      
IGx89
IGx89 commented Mar 7, 2020

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

serhalp
serhalp commented Nov 18, 2019

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

utPLSQL
wolframhaussig
wolframhaussig commented Mar 11, 2020

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

dkasak
dkasak commented Dec 12, 2016

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

risogolo
risogolo commented Aug 10, 2018

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?

tester
petrparolek
petrparolek commented Sep 24, 2019

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
skunk
etagwerker
etagwerker commented Feb 8, 2020

In the README.md:

To get the best results, make sure that you have coverage/.resultset.json in
your application directory. That way skunk 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 "

Improve this page

Add a description, image, and links to the code-coverage topic page so that developers can more easily learn about it.

Curate this topic

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."

Learn more

You can’t perform that action at this time.