-
# Summary
We're making incredible strides shipping features quickly, but this is resulting in deploying too-frequent regressions and bugs into production. To reduce the impact of these regressions whi…
-
## Description
As of this time, when using doctest with fixture classes, there is no way to write
common fixture teardown code outside of the fixture destructor.
When doing so with assertion macr…
-
Opening this issue to begin discussion on how we should handle testing with v2. Currently the unit tests return mocked data and integration tests require containerlab to be spun up.
I propose the …
-
Our fixtures are kind of ... a pain to deal with. The other day I suggested using [factoryboy](https://factoryboy.readthedocs.io/en/latest/) to generate all our fixtures.
I haven't used it much bef…
-
From #818, basis tests are now parametrized over a list of `Basis` objects instantiated with parameters that are stored in `tests/_basis_util`, e.g.
https://github.com/ComputationalCryoEM/ASPIRE-Py…
-
Adding new fixtures leads to trouble because we test some things on the fixtures directory. It's annoying to have to modify other tests to add new ones.
edaub updated
4 years ago
-
Fake and Secure data dump to support re-occurring headless test. Loadable with psql.
-
http://pytest.org/latest/fixture.html#fixtures gives some nice examples, but the tests don't have to be rewritten for `py.test` necessarily.
-
Currently wct's browser.js imports test-fixture in a pretty dynamic way. We should add a comment syntax or some other way to indicate a dependency so that we can notice that test-fixture is defined.
-
**Is your feature request related to a problem? Please describe.**
Currently, in a Pytest environment, we preload approximately 40 yaml config files when instantiating a `LazySettings` object for a t…