We want to try having system tests drive development, but we
don't want to add failing test cases to existing jobs. The
existing jobs need to move and stay at 100% as we use them
to gate other dev patches. So, this new job can be a landing
spot for these new CSIT tests that may not be ready on the
feature dev side.
The job can be run with the patch test using the gerrit
keyword "test-netvirt-tdd-wip".
The job can also be a place for new CSIT that is almost
ready, but might need a place to bake to ensure we iron
out all the kinks. For these cases, we'll have to run the
job manually. Or we can set some sort of non frequent
schedule.
Change-Id: Iccdb1c0be8f859e7806b66e0c97e52c6e326d82c
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
stream:
- oxygen:
branch: 'master'
- csit-blacklist: longevity gate sanity capwap centinel coe didm iotdm jsonrpc lacp netide
+ csit-blacklist: longevity gate sanity capwap centinel coe didm iotdm jsonrpc lacp netide tdd wip
csit-list: !include: csit-jobs-oxygen.lst
csit-sanity-list: '{csit-sanity-list-oxygen}'
csit-weekly-list: '{csit-weekly-list-oxygen}'
odl-snat-mode: 'conntrack'
- gate-minimal-cluster:
testplan: '{project}-{topology}-minimal-openstack.txt'
+ # Job for Test Driven Development with it's own testplan to run new/non-passing suites. scheduled manually.
+ - tdd-wip:
+ testplan: '{project}-{topology}-tdd-wip.txt'
+ schedule: ''
openstack:
- ocata:
- l2gw:
csit-list: >
netvirt-csit-hwvtep-1node-openstack-{os-branch}-gate-stateful-{stream}
+ - tdd-wip:
+ csit-list: >
+ netvirt-csit-1node-openstack-{os-branch}-tdd-wip-{stream}