py.test JIRA integration plugin, using markers
A pytest plugin for JIRA integration.
This plugin links tests with JIRA tickets. The plugin behaves similar to the pytest-bugzilla plugin.
The plugin does not close JIRA tickets, or create them. It just allows you to link tests to existing tickets.
Please feel free to contribute by forking and submitting pull requests or by submitting feature requests or issues to issues.
NOTE: You can set default value for run parameter globally in config file (option run_test_case) or from CLI --jira-do-not-run-test-case. Default value is run=True.
You can specify jira issue ID in docstring or in pytest.mark.jira decorator.
By default the regular expression pattern for matching jira issue ID is [A-Z]+-[0-9]+, it can be changed by --jira-issue-regex=REGEX or in a config file by jira_regex=REGEX.
It’s also possible to change behavior if issue ID was not found by setting --jira-marker-strategy=STRATEGY or in config file as marker_strategy=STRATEGY.
Strategies for dealing with issue IDs that were not found:
If you use decorator you can specify optional parameter run. If it’s false and issue is unresolved, the test will be skipped.
@pytest.mark.jira("ORG-1382", run=False) def test_skip(): # will be skipped if unresolved assert False @pytest.mark.jira("ORG-1382") def test_xfail(): # will run and xfail if unresolved assert False
You can disable searching for issue ID in doc string by using --jira-disable-docs-search parameter or by docs_search=False in jira.cfg.
def test_xpass(): # will run and xpass if unresolved """issue: ORG-1382""" assert True
Issues are considered as resolved if their status matches resolved_statuses. By default it is Resolved or Closed.
You can set your own custom resolved statuses on command line --jira-resolved-statuses, or in config file.
If you specify components (in command line or jira.cfg), open issues will be considered unresolved only if they are also open for at least one used component.
If you specify version, open issues will be unresolved only if they also affects your version. Even when the issue is closed, but your version was affected and it was not fixed for your version, the issue will be considered unresolved.
pip install pytest_jira
Create a jira.cfg and put it at least in one of following places.
The configuration file is loaded in that order meantioned above. That means that first options from global configuration are loaded, and might be overwritten by options from user’s home directory and finally these might be overwritten by options from test’s root directory.
See example bellow, you can use it as tempate, and update it according to your needs.
[DEFAULT] url = https://jira.atlassian.com username = USERNAME (or blank for no authentication password = PASSWORD (or blank for no authentication) # ssl_verification = True/False # version = foo-1.0 # components = com1,second component,com3 # strategy = [open|strict|warn|ignore] (dealing with not found issues) # docs_search = False (disable searching for issue id in docs) # issue_regex = REGEX (replace default `[A-Z]+-[0-9]+` regular expression) # resolved_statuses = comma separated list of statuses (closed, resolved) # run_test_case = True (default value for 'run' parameter)
Configuration options can be overridden with command line options as well. For all available command line options run following command.
Mark your tests with jira marker and issue id.
You can put Jira ID into doc string of test case as well.
Run py.test with jira option to enable the plugin.
In order to execute tests run