coverage
Here are 762 public repositories matching this topic...
Hello!
I think I've figured out a good way to get SimpleCov working with Spring. For my Rails application, preloading the app would require some classes in my ./app
directory, and this would cause some inaccurate coverage to be reported (any lines that were required during preloading were missing in the coverage.) I figured out how to fix this issue by starting SimpleCov in config/spring.rb
The features section in the docs states that nodemon is available in the project, when it's clearly not. It's not added as a dependency or as a command in the project. Maybe remove this from the docs or actually add nodemon?
Scenario
- JaCoCo version: 0.8.5 (latest)
- Operating system: Linux
- Tool integration: Maven
- Description of your use case: create aggregate report for multi-module Maven build
Current Behaviour
First report-aggregate creates an empty report. Then the documentation page at report-aggregate-mojo is without exa
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
In the following scenario, replacing the body of Child#one with super
causes a SystemStackError when Child#one is being called. However mutant does not detect that this error kills the mutation that replaces the method's body with super
. See https://github.com/matthias-g/mutant_super_bug for a running example.
class Parent
attr_reader :foo
def initialize(foo)
@foo = fo
-
Updated
Mar 11, 2020 - JavaScript
Basically we need to choose between:
class X {
private $foo;
public function __construct(string $foo) {
$this->foo = $foo;
}
public function getFoo(): string {
return $this->foo;
}
}
or:
class X {
/**
* @var string
*/
private $foo;
public function __construct(string $foo) {
$this->foo = $foo;
}
public f
Hello! I’ve looked at the Usage Guide (both the wiki page and the PDF) but neither of them explain how to get started. They both assume that the user already knows how to obtain and run OpenCover. I’ve added the OpenCover nuget package to my solution but I could not figure out how to go from there. The Usage Guide talks about a “console application” but there is no console application anywhere tha
-
Updated
Dec 31, 2017 - PHP
-
Updated
Jun 3, 2020 - CMake
Hi, I've been using this library for sending a coverage report from a dockerized build hosted in Travis-CI.
At first I was unable to understand why coveralls.io builds had a coverage report but not a branch name nor a commit msg. At the end I had to read the library's code and this article to unders
-
Updated
Jan 1, 2020 - Perl
vendorPath not match
When building github.com/AsynkronIT/protoactor-go
we got the following error:
vendor dependency golang.org/x/time:github.com/hashicorp/consul: commit='a86d11ec0aaadf6965014abd0030085d67454406', urls=[https://github.com/hashicorp/consul.git, git@github.com:hashicorp/consul.git]/vendor/golang.org/x/time/rate does not exist in transitive dependencies of github.com/hashicorp/consul#a86d11ec0
Adding documentation example of a working CI build using cirrus-ci.org (.cirrus.yml)
-
Updated
Jun 2, 2020 - Ruby
Suites like gcov works well if I execute many binaries (or the same binary with different arguments) in parallel, does kcov support this too? In particular, I'm interested in bash coverage.
For example, to have two scripts that source common.sh, and I execute them in two different shells, will the common.sh merged reports be OK? If not, what parts of kcov should be modified to support it?
Th
New Issue Checklist
- Updated fastlane to the latest version
- I read the Contribution Guidelines
- I read docs.fastlane.tools
- I searched for existing GitHub issues
Issue Description
When running fastlane swift and i
Based on the text at the bottom of https://docs.coveralls.io/supported-ci-services, my understanding is to use Coveralls with an unsupported CI provider, you need to set the other service_*
parameters in https://docs.coveralls.io/api-reference.
There doesn't currently appear to be a way to do this though which is preventing me from using this project.
Currently when choosing any of the other output formats it's not possible to get the text report printed to stdout or even a file.
I've tried the following, but neither work.
$ gcovr --sonarqube coverage.xml --output
usage: gcovr [options] [search_paths...]
gcovr: error: argument -o/--output: expected one argument
$ gcovr --sonarqube coverage.xml --output -
(WARNING) --output='-' op
-
Updated
May 20, 2020 - Java
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
-
Updated
Apr 16, 2020 - JavaScript
In the "Tracking Coverage as-a Service" section:
https://github.com/dwyl/learn-istanbul/tree/bb027a62b40558ad1717fd8f168291777b95b8cd#tracking-coverage-as-a-service
We are currently advising people to use the "old" way:
We can simplify this a lot by simply running the bash command:
!
-
Updated
Apr 1, 2020 - Kotlin
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?
Improve this page
Add a description, image, and links to the coverage topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the coverage topic, visit your repo's landing page and select "manage topics."
Core functionality, such as the built in test interfaces and assertions, should be available to import through the base Intern export.
At least the test interfaces (
object
,bdd
,tdd
),assert
, andexpect
should be exported. The implementer should also verify that the necessary types are exported