-
I recently worked on a test that involved using a setup step to untar a rather large database (~8 GB), [see here](https://github.com/nf-core/modules/blob/master/modules/nf-core/krakenuniq/preloadedkra…
-
Best explained with a failing test, see:
https://github.com/jinty/pytest/commit/c0048b115314dd4a54d1fea5032d85f52efd221b
or inline for the lazy:
```python
import pytest
@pytest.fixture(sc…
jinty updated
5 years ago
-
I realize there's a min pytest version specified in requirements but it seems to be incorrect. The tests seem to run fine at anything matching pytest >= 3.5.0. In 3.5.0 the order of fixture instantiat…
-
With a stack like the following `gt`/`wt` will pick frame 38 (`fixtures.execute`):
```
[32] …/project/.venv/lib/python3.7/site-packages/_pytest/python.py(1442)setup()
-> fixtures.fillfixtures(s…
-
pytest fixtures decorated with @freeze_time do not have time frozen:
`
@freeze_time('2018-01-01') `
`@pytest.fixture `
`def sample():`
`print(datetime.datetime.now(datetime.timezone.utc)…
-
I am missing something very obvious: Below is my use case as seems best to explain with example:
- a fixture to create a bunch of parameters
```
@pytest.fixture(name="hc_tags", params=[("Label", TR…
-
## 🐛 Bug
If a pytest test uses `async` stuff, there's no apparent way to run the test properly. If the test function is defined to be synchronous and calls `asyncio.run()` internally, it raises `Ru…
-
Adding Fixtures to a parametrization of a test function via `pytest.mark.usefixtures` has no effect. The fixtures are not executed and are missing from `request.fixturenames`.
Example:
```python
…
-
Consider this test case:
``` python
import pytest
CALL_COUNT = 0
@pytest.fixture(scope="module")
def fixture(_dynamic_param):
global CALL_COUNT
CALL_COUNT += 1
def pytest_generate_test…
-
If all the parameters to a fixture function have default values, `pytest.fixture` handles them appropriately but `pytest_cases.fixture` does not.
```
import pytest
import pytest_cases
# This w…
vyasr updated
2 years ago