-
In #224, @matklad suggested using "test coverage marks" to manually track test coverage:
https://github.com/rust-analyzer/rust-analyzer/blob/ef782adc293deb287128f005dbab2038ba3ccdc1/crates/test_uti…
-
The first issue that I ran into, trying to copy the [Booking example](https://github.com/revel/examples/blob/master/booking/app/controllers/app_test.go) in order to use `go test` for full coverage. Wh…
-
How much of the cellbase code is executed during the unit tests?
[I added the jacoco library to a branch](https://github.com/julie-sullivan/cellbase/pull/1/files), and ran some reports to get the p…
-
In addition to adding tests for any new features, the test coverage for all the existing features should be expanded as much as possible.
- [ ] Restructure test suite, breaking into separate files wh…
-
```
runtests.py -coverage
Lack of coverage quite often means bugs (and usually trivial bugs, so
improving coverage gives good payoff for little work).
24 75% mpmath.__init__ (c:\source\mp\…
-
A lot of the features built quickly for our CFP lack proper test coverage.
skade updated
10 years ago
-
- 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.