-
This came up at the Dev call today, but we should consider putting together a standard Contribution Guide and include it in the repo and RTD. It should include:
- Code formatting standards (`black`)…
-
Please tag all testing commits to this issue.
-
Right now we're sort of using hardhat coverage. We can use `Forge coverage` to generate coverage reports and `Coverage gutters` in VSCode to highlight uncovered lines in IDE. I'd also push the `lcov` …
-
Package | Line Rate | Branch Rate | Complexity | Health
-------- | --------- | ----------- | ---------- | -----…
-
It is unclear to me how to setup tox, pytest-cov, coverage or sphinx-gallery so that code in `examples/` is included when calculating the coverage information. I searched the docs and around the web a…
-
Increase coverage to benchmark 85%+
mmcky updated
3 years ago
-
We need a strategy for testing our metering coverage. One way is to enable the host to run in "calibration mode", where we turn on cpu and memory counter (like what we do in benches, but for end-to-en…
-
The codecov tool is working for Icepack and CICE, (see #434, #436) and a handful of people can run the testing. We should next evaluate the codecov results and see if we can improve testing coverage.…
-
- [ ] Happy flow
- [ ] No pre-prepare
- [x] pre-prepare ok, no quorum for prepare causing change round
- [x] wrong pre-prepare, no later prepare quorum
- [ ] wrong pre-prepare with later prep…
-
We need to provide code coverage of the code in the project.
We can spilt it between backend and front end.
We ideally should test as we go. Meaning that we mock feature functions and simulate i…