-
## Description
To supplement unit tests for components, we should add a suite of E2E tests that go through the major workflows in the app. This will allow us to test many components that are often use…
-
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…
-
If continuous integration is implemented, perhaps it would be useful to design this in such a way that it would also measure the extend to which testing covers the code, similar to:
- https://coverall…
-
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…
-
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...)
-
Our testing coverage is sitting at ~82% as of this writing, we should try to improve that, so we should have some goals:
- [x] 85% coverage
- [ ] 90% coverage - https://github.com/mitodl/mitxpro/…
-
We need to improve testing coverage, both in terms of unit and regression tests. Currently, we only run regression tests using the examples found in the examples directory. Furthermore, these test are…
-
-
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…