-
The test coverage status can be estimated by running `coverage html/xml/report` from the root directory of the project. The below snapshot shows the stats as of July 22, 2024.
*Improving coverage*
…
-
In #168, coverage _appears_ to go way down, but this is not really due to new code. In particular, we need to be covering `Async` versions of things in `actor.py` and some LMDB stuff in `store.py`.
-
Note: some of this missing coverage will be implicitly covered by upstream packages such as `@tevm/memory-client` which has extensive integration testing. We still want to get 100% unit test coverage …
-
Coverage testing isn't working for me. When I run with coverage, the progress monitor spins indefinitely and no coverage information is provided. The test results are displayed correctly if I run wit…
-
I see that the test coverage might not be where it should be, considering that bns is a core contract.
-
I put this on hold for now until refinements are complete on the current components. It will also need to be added to as so far the tests are currently only unit testing of the frontend components.
-
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…
-
LNV2 is still missing the following tests. For the devimint tests to work we need to enable lnv2 in devimint.
- [x] (devimint) gateway registration sanity test: https://github.com/fedimint/fedimint…
-
Additional testing scenarios to add to integration tests:
1. Deposit, iterative self transfer. Client performs self transfer to itself iteratively until the locktime reaches the current blockheight…
-
More E2E tests in Cypress for key workflows such as interacting with variables. we already have a bunch of cypress tests, we should ensure core scenarios are covered. @SamIam4Hyma can provide a good s…
six7 updated
20 hours ago