-
# Problem
The text reporter has truncated output in Node 6.
## Minimal Test Case
[Test case repo](https://github.com/MitMaro/IstanbulTruncateBug)
```
git clone https://github.com/MitMaro/IstanbulTr…
-
I am getting the error Workflow failed! Resource not accessible by integration
I am using the following workflow. Everything works fine if I comment out the Comment Coverage step.
```
name: Li…
-
* **I'm submitting a**
- [x] bug report
* **What is the current behavior?**
when I run Istanbul code coverage using:
`ng test --source-map --code-coverage`
tests do not return exit code 1 on …
-
- [x] Select and configure Testing library
- [x] Integrate with Travis to ensure that tests are run when branches are pushed/merged
- [x] Install and configure Coveralls to monitor code coverage
- [x]…
-
Add a `--coverage` argument to `zig test` and have it generate a nice report.
Related:
* #20989
* #20992
-
`karma-coverage` allows to specify some coverage checks, so karma fails if the minimal coverage isn't achieved.
Could you implement that for this plugin as well?
-
We need a bunch of test cases.
coverage run --branch test_watson.py
-
I tried several permutations on the scripts:
```
"test:coverage": "react-scripts test -- --coverage --env=jest-environment-jsdom-fourteen",
"test:coverage": "cross-env CI=1 react-scripts test -- --…
-
Right now it appears (at least with Travis) that coveralls always does comparisons against master when deciding how much coverage increases/decreases. This is problematic on an active project where t…
-
Improve the coverage with mocha :
- [ ] 100% of lines of code
- [ ] 100% of statements
- [ ] > 95% of branches