Overwrite allure history id with testcase full name and testcase id if testcase has id, exclude parameters.
When the library is not installed,the historyId of the test cases generated by Allure is based on dynamic parameters within the test case, and each execution is not considered the same test case. After installing the library, when a test case id is configured, even with dynamic parameters, it will be recognized as the same test case.
Installation
You can install “pytest-allure-id2history” via pip from PyPI:
$ pip install pytest-allure-id2history
Usage
import random
import pytest
@pytest.mark.parametrize('arg', [
random.randint(0, 9999)
], ids=['some-id'])
def test_foo(arg):
print(f'Testing foo with {arg}')
Contributing
Contributions are very welcome. Tests can be run with tox, please ensure the coverage at least stays the same before you submit a pull request.
License
Distributed under the terms of the MIT license, “pytest-allure-id2history” is free and open source software
Issues
If you encounter any problems, please file an issue along with a detailed description.
Metadata
Release files for pytest-allure-id2history 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytest_allure_id2history-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / pytest_allure_id2history-0.1.2-py3-none-any.whl
| Download URL | pytest_allure_id2history-0.1.2-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e512af6cf52a595c9b2a64288a2e89f405bfeee5d8177ae2825e8ff517f4a60b
|
|
BLAKE2b-256 checksum How to use checksums |
e9dc86cf7748148409358365ab931581352896a603d44e066650dc1b7a8b696d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for pytest-allure-id2history 0.1.2
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.