-
- defect creation
- defect filter creation, update, deletion
- defect list filtered according to the applied filter
- defect selection
- defect update, including comment creation, edition and deletion…
-
If some software really needs to be reliable, that's the OS. We need to document and tests all the processes, and we must work to achieve a 100% testing coverage to be sure there's no hidden bugs.
-
-
ie, move beyond just doctests.
-
- Depends on #7 or it will be a shame to show
- https://github.com/codecov/example-android
- Setup badge to readme
-
-
## Issue
Low Coverage in some tests.
### Description
We are not checking all the fields that are being sent from our API and thus the test coverage is low for some tests. Please have a look into …
-
### Describe the bug
If you use istanbul coverage (required for browser mode), override the coverage `excludes`, and use `vi.hoisted`, then your test runs fail with cryptic syntax errors.
This wor…
-
I am building a Go provider for [Pruner][1] (a CLI that runs only the tests that ran through the lines you changed, saving you time).
For that, I need to be able to see per-test coverage. Not just …
-
Tracks work to implement a dedicated code coverage subcommand of `swift test` that can:
1. Show the path to code coverage files (existing `--show-codecov-path` option)
2. Collate .profraw files on…