-
Test coverage for certain functions needs to be improved to pick up any issues or changes in the future that could affect core functionality.
**Functionality Tests**
These ensure given correct da…
-
Currently, code coverage includes both fuzz and concrete tests. The fuzz tests require that functions are not reverting. That's why we use `assume` and `bound` in them. Thus, they only test for non re…
-
We have made tremendous progress on testing in the bridge: cross-test, providertest and replay testing have made it much easier to write and maintain high quality tests of the bridge. cross-test has c…
-
Hola profes, con @BautistaTorregiani hoy nos pusimos con la documentación de las estaciones y ya terminamos ese tema. Ahora, se nos presentó el problema de que cuando ejecutamos devtools::test_coverag…
-
The manual testing section should include more comman…
-
Our unit test coverage is at 70%. That's not great. I would really like to see it as close to 100% as possible before we do too much further development; it makes it much easier to be confident in PRs…
-
The current suite of tests for the class `Material()`, included in the file _test_material.py_, covers only some of the possible class capabilities.
- In `test_material_from_coeff()` and `test_mate…
-
The manual testing section should include mo…
-
In addition to running tests, we should start recapturing coverage results from the tests (formerly handled by Coveralls) and include this in the script as well. Per #1146, once we have coverage captu…
-
- [ ] App Boot
- [ ] Helpers / Database
- [ ] Helpers / Encryption
- [ ] Helpers / Logger
- [ ] Helpers / Query
- [ ] Helpers / Schema (pay special attention to data validation)
- [ ] Helpers / …