test-coverage
Here are 86 public repositories matching this topic...
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 = foHi, 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
Issue description or question
The coverage markers usually remain green for the lines that contain the test declaration in Jest. This is usually not a problem until those tests are collapsed (folded). When the tests are folded, then it becomes more difficult to tell that the tests did not run just by scanning the coverage markers.
For example:
. Sent out in fragments of 4M.
But 4 * 2**20 is 4M (also DATALEN used in Case 9.3.9 is 4M).
Please change case description to the (4M).
Thank you.
P.S. Also in all cases in 9 chapter probably should be fixed repeating of message word:
...text message message with message
-
Updated
Mar 22, 2020 - Go
Description
Minor cleanup of the preview coverage feature to remove some tech debt (code structure, content security cleanup, etc). This came to my attention via an error that is appearing in the test builds.
ryanluker.vscode-coverage-gutters created a webview without a content security policy: https://aka.ms/vscode-webview-missing-csp
Work
- add a content security poli
We have the openlibm files, so why don't we actually build a libm that can be used alongside libc?
Probably deserves a standalone meson.build file if possible (with wrap?)
-
Updated
May 13, 2020 - JavaScript
-
Updated
Dec 21, 2018 - Python
-
Updated
Oct 8, 2018 - Ruby
-
Updated
Dec 16, 2019 - Go
-
Updated
Apr 26, 2020 - Java
-
Updated
Oct 8, 2018 - JavaScript
Steps required to reproduce the problem
- composer create-project "symfony/skeleton:^4.0" symfony4
- cd symfony4
- composer require codeclimate/php-test-reporter --dev
Expected Result
- Successfully installation
Actual Result
Your requirements could not be resolved to an installable set of packages.
Problem 1
- codeclimate/php-test-reporter v0.4.4
-
Updated
Aug 9, 2019 - Kotlin
Provide additional comparision against mutation testing, by pitest framework.
Let's see who is the boss agian!
-
Updated
Apr 26, 2018 - C++
-
Updated
May 16, 2020 - Python
-
Updated
Feb 26, 2018 - Python
-
Updated
Nov 17, 2018 - Java
-
Updated
Sep 10, 2019 - HTML
-
Updated
Nov 27, 2019 - Python
-
Updated
Jul 2, 2019 - HTML
if a number isn't passed in it should default to random, but if it is it should just make sure that number is count digits long
-
Updated
Oct 9, 2019 - Kotlin
Improve this page
Add a description, image, and links to the test-coverage topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the test-coverage topic, visit your repo's landing page and select "manage topics."
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
./appdirectory, 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 inconfig/spring.rb