-
Para realizar #58 necesitaremos un workflow, este debera de actualizar el coverage report si no hay fallos en los tests
-
Test coverage has some gaps, and at least one bug has been hidden by it (#235)
**electrostatics.jl**
- [ ] [`*(a::Float64, ews::GGEwaldSum)`](../blob/master/src/electrostatics.jl#L31)
**energ…
-
- [x] It is including node_modules and other irrelevant files when I run it locally.
- [x] The file names can not be read, as they are cut off. ( An example name: "...g.stories.tsx" )
- [ ] Is it no…
-
## Issue
* We don't exactly know how much of our codebase is covered to ensure there is no regression in functionality. We have a command that can be found in the `package.json` called `"test:coverag…
-
**Is your feature request related to a problem? Please describe.**
We would like to generate code coverage metrics
**Describe the solution you would like**
- Add code coverage plugin to SBT
…
-
Hi!
It's really great of you to have started such a project.
It would be great if there was a coverage map.
That way you can see which parts of the world have not yet been measured, just like wit…
-
[This post by Hynek](https://hynek.me/articles/ditch-codecov-python/) describes a technique for aggregating coverage results across independent jobs. Let's explore applying that technique to skeleton-…
-
We have pretty limited test coverage at the moment, only covering the pricing api.
Would love to expand test coverage to the IV calcs and greeks. Some of this is difficult as we have some little…
-
# SDK
## Unit testing
- address
- bcs
- crypto
- transaction
- utils
## E2E testing
- all client methods
#SDK-Kit
## E2E testing
- all hook methods
-
The various linters have been replaced by ruff (thanks to @L77H).
* We should have a look at the ruff rulesets and decide which are most interesting (and best value for effort): https://docs.astral…