pytest-initry
Plugin for sending automation test data from Pytest to the initry.
Install and setup:
- Install:
pip install pytest-initry - Configure pytest.ini:
[pytest] initry_host = localhost initry_port = 8000 initry_grpc_port = 50051 initry_batching = False initry_junit_xml_only = False
- CLI can also be used, but it's not the preferred method. The arguments will be the same as those mentioned for the pytest.ini config file.
pytest --initry-host=localhost --initry-batching=True
Arguments:
initry_host
Initry API Backend hostname. Use the same value as INITRY_API_HOST for backend .env and NEXT_PUBLIC_INITRY_API_HOST for frontend .env.
Example: localhost, 192.168.1.2, etc.
initry_port
Initry API Backend port. Use the same value as INITRY_API_EXTERNAL_PORT for backend .env and NEXT_PUBLIC_INITRY_API_EXTERNAL_PORT for frontend .env.
Example: 8000, etc.
initry_grpc_port
Initry gRPC Backend port. Use the same value as INITRY_GRPC_EXTERNAL_PORT for backend .env.
Example: 50051, etc.
initry_batching
Batching mode: Use only if you have thousands of very fast unit tests. Data from the plugin to the Initry backend will be sent in batches.
Will not work with initry_junit_xml_only
Example: True, False.
initry_junit_xml_only
Real-time mode will be disabled, only the Pytest XML JUnit report will be sent at the end of the test run.
Will not work with initry_batching
Use together with pytest argument --junitxml=your_xml_file.name.xml
Example: True, False.
Examples:
pytest: Pytest will be executed in real-time mode.
pytest (with initry_batching=True): Pytest will be executed in real-time mode, but data will be sent to the server in batches to reduce network overhead. Real-time data will only display task finalized statuses without the 'running' state.
pytest --junitxml=test.xml: Pytest will be executed in real-time mode, and additional information will be collected from the generated JUnit XML file after the test run finalization.
pytest --junitxml=test.xml (with initry_junit_xml_only=True): Pytest will be executed without providing real-time data, and information will be gathered after the test run ends using the generated JUnit XML file.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for pytest-initry 0.4.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 | Actions |
|---|---|---|---|---|
| pytest_initry-0.4.0.tar.gz | 10.5 kB | Without provenance | Details for pytest_initry-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pytest_initry-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for pytest_initry-0.4.0-py3-none-any.whl |
Total release size: 27.0 kB
Release files / pytest_initry-0.4.0.tar.gz
| Download URL | pytest_initry-0.4.0.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
590736ca697d33c336dea52e0eb19822bac21c752b5f10be561a5152e5930db9
|
|
BLAKE2b-256 checksum How to use checksums |
91c52b323a329b687350480856842899f56e03bc987951a7b2ccbbb4b7d09ba0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.2 CPython/3.10.4 Linux/6.5.0-28-generic
|
Release files / pytest_initry-0.4.0-py3-none-any.whl
| Download URL | pytest_initry-0.4.0-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1475ffeb550ac8d3516b55dc4ae6b5747ac55145d3f7dcd2e1c8297a806a495
|
|
BLAKE2b-256 checksum How to use checksums |
5b7938e63ccd45ee42033e835dedb0977566b581c8b37f5fcaa51bad8a894303
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.2 CPython/3.10.4 Linux/6.5.0-28-generic
|
Security for pytest-initry 0.4.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.