-
The current amplicon coverage script devised by @dr-david won't work for all sets of primers and corresponding amplicons. The current logic exploits non-overlapping amplicon regions/positions to ident…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Describe the feature
Today we don't have information regarding coverage in SonarCloud.
-
I have an issue loading a previous session from a session xml file.
In a previous session, I changed the track height and set track colors to correspond to their conditions. However, when I reload …
-
### Clear and concise description of the problem
What if Vitest kept track of which lines each test runs through. That way, the "--changed" flag would be truly only "changed", and could save a huge…
-
Hi, I'm having some problems with this.
No folders 5_Plastome_Finishing, Coverage_Analysis, and Final_Assembly appear, so I can't see the results of the assembly.
[C2-try_Fast-Plast_Progress.log](ht…
xhx-1 updated
3 weeks ago
-
Hi,
I'm trying to use coverage to cover tests written in unittest in a production framework, with several constraints, but it fails with this error:
` raise NoSource(f"No source for code: '{fi…
-
### Do you want to request a *feature* or report a *bug*?
Feature
### What did you expect to see?
- Coverage report
- Static and dynamic analysis (may be more appropriate for https://g…
-
It would be nice to be able to exclude some source files from coverage. A good example is https://github.com/timholy/ProfileView.jl, where the `precompile.jl` file only runs when the package is being …
-
Right now, the project's README file shows a hardcoded 100% coverage badge (see [here](https://github.com/Flexonze/django-auto-actions/blob/main/README.md?plain=1#L7)). To provide more accurate and dy…
-
In larger programs and real-world projects it's often difficult to know whether a certain part of code was actually analyzed or not.
Dead code warnings provide only partial information because the la…