|
4 days ago | |
---|---|---|
doc | 6 days ago | |
playbooks | 9 months ago | |
releasenotes/source | 6 months ago | |
roles | 4 days ago | |
tempest_skip | 6 days ago | |
.coveragerc | 1 year ago | |
.gitignore | 1 year ago | |
.gitreview | 1 year ago | |
.zuul.yaml | 6 months ago | |
README.rst | 3 months ago | |
requirements.txt | 3 months ago | |
setup.cfg | 6 days ago | |
setup.py | 11 months ago | |
test-requirements.txt | 3 months ago | |
tox.ini | 6 months ago |
openstack-tempest-skiplist will generate a skip list to be executed by tempest
Installing from git and virtualenv:
$ git clone https://opendev.org/openstack/openstack-tempest-skiplist
$ cd openstack-tempest-skiplist
$ virtualenv .venv
$ source .venv/bin/activate
$ pip install .
After edit your file, you can check if it is valid with the following command:
$ tempest-skip validate --file file.yaml
A simple example of the structure of the yaml file expected by tempest-skiplist. For more information about each field, visit the documentation <https://docs.openstack.org/openstack-tempest-skiplist/latest/yaml/formatting.html> website:
known_failures:
- test: 'full.tempest.test'
bz: 'https://bugzilla.redhat.com/1'
lp: 'https://launchpad.net/bugs/1'
deployment:
- 'undercloud'
- 'overcloud'
jobs:
- job1
- job2
reason: 'default reason'
releases:
- name: master
lp: 'https://launchpad.net/bugs/2'
reason: 'Some reason'
- name: train
bz: 'https://bugzilla.redhat.com/train1'
- name: ussuri
bz: 'https://bugzilla.redhat.com/ussuri1'
In the above example, the test full.tempest.test will be executed by tempest in both deployments, undercloud, and overcloud (depending on the job). It will also be skipped in the releases master, train and ussuri, specifically in jobs job1 and job2. It will not be skipped in any other job, no matter what the release is.
Removing the list of jobs, means it will be skipped everywhere.