-
This issue is a progress tracker on the potential to improve the test coverage in RosettaSciIO:
**Formats missing test files**:
- [ ] netCDF
**Formats with coverage below 80%**:
- [ ] digital-…
-
Coverage is key, just set it up.
- https://github.com/istanbuljs/nyc
Some kind of reporting action? That would be great.
https://developer.github.com/v3/checks/
-
For the moment, theres no single test of the integrity of the app. This could be a code debt.
-
Ging mit dem Cypress-Umbau verloren. War vorher in Angular integriert und nutzte outdated packages (istanbul-instrumenter). Das muss vermutlich iwie anders laufen.
-
Next steps
1- Blog post to point to the issues we have open to encourage external help.
-
It would be nice to add targets/properties to allow code coverage report generation out of the box in Arcade. Bonus points if it produces a format that AZDO pipelines can ingest by default.
After f…
-
## Feature Request
**Feature description :**
It would be great to have the tool output "code coverage" stats if possible - number of resources in the plan vs. number of resources covered by tests …
-
Dear Panacus,
Thank you for developing such a great program.
I’m interested in testing the "Ordered Pangenome Growth Statistics" for a PGGB GFA file. However, the manual only provides guidance f…
-
The current building for coverage implementation works by rewriting the source files adding some instrumentation statements that later are used to determine the code lines that were executed durin…
-
A couple of tests are failing with the following mismatch in the output:
```
-Preprocessing library for plain-0.1.0.0...
-Building library for plain-0.1.0.0...
-Preprocessing test suite 'test' for…