This release is a pre-release and may not be stable for production use.
Intro
PyTest plugin for bugzilla integration. This plugin currently assumes the following workflow:
bug_status in [‘NEW’, ‘ASSIGNED’, ‘ON_DEV’] means the bug is known and is being worked on and therefore the test should be skipped and will be.
bug_status not in [‘NEW’, ‘ASSIGNED’, ‘ON_DEV’] means the bug is in a state ready for QE and the test will be run and reported on.
Please feel free to contribute by forking and submitting pull requests or by submitting feature requests or issues to issues
Requires
pytest >= 2.2.3
python-bugzilla >= 0.6.2
six
Installation
pip-python install pytest_marker_bugzilla
Usage
Create a bugzilla.cfg in the root of your tests. You can also put it under $HOME and /etc.
[DEFAULT] bugzilla_url = https://bugzilla.fqdn/xmlrpc.cgi # Username for authentication bugzilla_username = USERNAME (or blank for public bugs) # Password for authentication bugzilla_password = PASSWORD (or blank for public bugs) # Version of your product bugzilla_version = X.Y (or blank if not relevant) # Tuple of fixed_in and target_release attribute of bug bugzilla_loose = (leave blank for default)Options can be overridden with command line options.
py.test --helpMark your tests with bugzilla marker and bug id(s).
@pytest.mark.bugzilla('bug_id', ...)In order to skip the test, all of the specified bugs must lead to skipping. Even just one unskipped means that the test will not be skipped.
Run py.test with bugzilla option to enable the plugin.
py.test --bugzilla
Conditional guards
The conditional guards, are functions which can xfail or skip the test when condition is met.
@pytest.mark.bugzilla(1234, skip_when=lambda bug: bug.status == "POST")
@pytest.mark.bugzilla(
567, xfail_when=lambda bug, version: bug.fixed_in > version
)
The guard is a function, it will receive max. 2 parameters. It depends what parameters you specify.
The parameters are:
bug - specific BZ bug
version - tested product version
Order or presence does not matter.
Test library
When you do changes please make sure that you pass current tests.
tox
Please also try to cover new features by writing new tests.
Enjoy.
Metadata
Release files for pytest-marker-bugzilla 0.9.1.dev2
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-marker-bugzilla-0.9.1.dev2.zip | 17.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytest_marker_bugzilla-0.9.1.dev2-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 24.5 kB
Release files / pytest-marker-bugzilla-0.9.1.dev2.zip
| Download URL | pytest-marker-bugzilla-0.9.1.dev2.zip |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
49593971c81ff551b575d29ac43932c1a3a9f7c8592d78882c5673c0d6cbdc1b
|
|
BLAKE2b-256 checksum How to use checksums |
938a459f9fb0ab5df3e3f64c8f2cea7f687a3e40e82f35b9e6755bf6b0b2162a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.4.2 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.2
|
Release files / pytest_marker_bugzilla-0.9.1.dev2-py2.py3-none-any.whl
| Download URL | pytest_marker_bugzilla-0.9.1.dev2-py2.py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b9f38da7f4370395e4de95e6d651ecf1f5fea6b03719b67ec955acb3ce65782c
|
|
BLAKE2b-256 checksum How to use checksums |
41e1be19dfea1244eed96a58bebd75bb5ec5c5373f5171bcd0edea69d39d8011
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.4.2 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.2
|
Security for pytest-marker-bugzilla 0.9.1.dev2
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.