-
rimio updated
3 years ago
-
Ignore UI testing for now; might be some new challenges for testing other parts though.
- For API calls, query live server with development API key. See if we can find a non-working account ID so w…
-
Collect coverage information at end of tests.
https://www.veripool.org/projects/verilator/wiki/Manual-verilator
1. Pass --coverage option to verilator in makefile
2. Modify c++ test harness to …
-
-
I would love a feature that would quickly show you what requests in a collection don't have tests. Right now, I think, the only way to see this is looking at each request. Let me know if I'm missing s…
-
We should write unit tests to verify the functionality in our lib.
We should also determine the code coverage, to check all paths are covered.
Note: the unit tests _may_ form part of the documen…
-
Unit tests have fallen behind while we were under the crunch to get something up and running.
Post refactor, functions and methods have been refactored so much that we currently sit at 0% test cove…
-
Generate Coverage report
---------------------
This should nearly at the end as it messes up the build repositories. It should be something similar to:
```
stage ('Test coverage') {
def re…
-
Need to change the total number of coverage lines.
ghost updated
2 years ago
-
We should bring code coverage up to 90% on all repos, and while we're at it make Travis CI make tests in a real-life case. (create mysql db, do migrations, make mock client...)