pytest-fixtures
Common fixtures for pytest
To use, just install it and pytest will automatically detect and load all fixtures:
pip install pytest-fixtures
To install automatically, add it to your test requirements in tox.ini or setup.py.
No Dependencies
This package does not depend on any other packages and never will. It uses standard libraries or uses run-time imports and therefore it is lightweight to add to any project. As for which external run-time dependency a fixture needs, that is documented here and shouldn’t matter as you would only use the fixtures that your project already has dependencies on.
Standard Fixtures
Fixtures based on standard Python libraries
test_data
To get path, read, and write test data in tests/data folder, use the test_data fixture.
First, setup the path to test data path in tests/conftest.py:
from pathlib import Path
from fixtures import TestData
TestData.BASE_PATH = Path(__file__).parent / 'data'
And then get path to data files in tests/data using test_data fixture:
def test_integration(test_data):
obj = MyClass(test_data.path('sample.csv'))
To write out test data:
def test_integration(test_data):
output = run_cli()
test_data.write('test_integration.output', output)
Then read the test data to assert:
def test_integration(test_data):
output = run_cli()
expected_output = test_data.read('test_integration.output')
assert expected_output == output
Click Fixtures
Fixtures for Click <http://click.pocoo.org/>
cli_runner
To invoke, assert exit, with stdout/stderr outputs on error:
.. code-block:: python
- def test_cli(cli_runner):
result = cli_runner.invoke( … ) # Prints out stdout/stderr from result with headings result = cli_runner.invoke_and_assert_exit(0, … ) # Same as above and asserts exit code == 0
Links & Contact Info
Metadata
Release files for pytest-fixtures 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pytest-fixtures-0.1.0.tar.gz | 6.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytest_fixtures-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.2 kB
Release files / pytest-fixtures-0.1.0.tar.gz
| Download URL | pytest-fixtures-0.1.0.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28f13dc9fb9206f4a5fba1a100e1b3de20fbfa37a7af440ca07222fa45b85b7b
|
|
BLAKE2b-256 checksum How to use checksums |
f7253b7527e005df1dfe040091c3fc6ce75a0670c8e458773678f96d184b3017
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/39.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.7
|
Release files / pytest_fixtures-0.1.0-py3-none-any.whl
| Download URL | pytest_fixtures-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8372ad1cd6dafd7e53b183b8601d1a85cda7bd829e7f73fae18416e95d270a3e
|
|
BLAKE2b-256 checksum How to use checksums |
0cd875876c6c77d4f79faaf7ecef0c6532820e4ade5936f4797a8dd4c1ff79db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/39.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.7
|
Security for pytest-fixtures 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.