Allure Nose Adaptor
It is a port of pytest-allure-adaptor for nose framework.
Usage
nosetests --with-allure --logdir=/path/to/put/results
nosetests --with-allure --logdir=/path/to/put/results --not-clear-logdir
Option “–not-clear-logdir” is useful with option “–processes” to prevent cleaning of logdr at the end of testing.
Supported features
Attachment
To attach some content to test report:
import nose
def test_foo():
nose.allure.attach('my attach', 'Hello, World')
Step
To divide a test into steps:
import nose
def test_foo():
with nose.allure.step('step one'):
# do stuff
with nose.allure.step('step two'):
# do more stuff
Can also be used as decorators. By default step name is generated from method name:
import nose
@nose.allure.step
def make_test_data_foo():
# do stuff
def test_foo():
assert make_some_data_foo() is not None
@nose.allure.step('make_some_data_foo')
def make_some_data_bar():
# do another stuff
def test_bar():
assert make_some_data_bar() is not None
Environment
You can provide test environment parameters such as report name, browser or test server address to allure test report.
import nose
def test_dummy():
nose.allure.environment(report='Allure report', browser=u'Firefox')
Severity
Any test, class or module can be marked with different severity:
import nose
class TestBar(object):
@nose.allure.severity(nose.allure.severity_level.CRITICAL)
def test_bar(self):
pass
# custom severity
@nose.allure.severity("hard")
def test_bar(self):
pass
To run tests with concrete priority:
nosetests my_tests/ --with-allure --logdir=tmp --severity="critical, hard"
Issue
Issues can be set for test.
import nose
@nose.allure.issue('http://jira.lan/browse/ISSUE-1')
def test_foo():
assert False
Features & Stories
Feature and Story can be set for test.
import nose
@nose.allure.feature('Feature1')
@nose.allure.story('Story1')
def test_minor():
assert False
class TestBar(object):
@nose.allure.feature('Feature2')
@nose.allure.story('Story1')
def test_bar(self):
pass
To run tests by Feature or Story:
nosetests my_tests/ --with-allure --logdir=tmp --feature="Feature1, Feature2"
nosetests my_tests/ --with-allure --logdir=tmp --feature="Feature1, Feature2" --story="Story1, Story2"
Metadata
Release files for nose-allure-plugin 1.0.6
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 | |
|---|---|---|---|---|
| nose-allure-plugin-1.0.6.tar.gz | 5.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nose_allure_plugin-1.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.7 kB
Release files / nose-allure-plugin-1.0.6.tar.gz
| Download URL | nose-allure-plugin-1.0.6.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2f3bd84dfca14d58beca2c22e14837442730c10bef2c5e4c53a74c9b93900932
|
|
BLAKE2b-256 checksum How to use checksums |
bbc742aea2c81a54e3c817e55f8c107731f60722e37d0c3845a936d05375b2c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.5
|
Release files / nose_allure_plugin-1.0.6-py3-none-any.whl
| Download URL | nose_allure_plugin-1.0.6-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2005aadc21d72b6fe2b398440dd65f1a975dac38e32bd30cdbab132c4d45b7e7
|
|
BLAKE2b-256 checksum How to use checksums |
641e83b70a6e7da9dee65502684e9cdd36876c9f98149088b243b9c3efc074bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.5
|
Security for nose-allure-plugin 1.0.6
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.