(2014/01/22 2:56), Lucas Eznarriaga wrote:
Hi,
For step 3/5, is the right procedure. Or is there a way to use a cmd to
run all the tests and use a different mechanism to specify a filter for the
tests to be run.
I don't know if Tempest allows you to filter for the tests to be run.
tempest defines some sets of tests like smoke-serial in tox.ini [1].
We can use tox -e smoke-serial or corresponding testr command like
testr run '(?!.*\[.*\bslow\b.*\])((smoke)|(^tempest\.scenario))'
to run a specific set of tests.
The command runs tests with smoke tag and all tests from
Hi,
For step 3/5, is the right procedure. Or is there a way to use a cmd to
run all the tests and use a different mechanism to specify a filter for the
tests to be run.
I don't know if Tempest allows you to filter for the tests to be run.
I'm following these steps to configure Jenkins but I
For vmware minesweeper ,we filter tests following way:
1. testr list-tests alltests
2. exclude-tests (file with test names we want to filter)
3. alltests - excludetests = tests_to_be_run
4. testr run —load-list=tests_to_be_run
hope that helps
On Jan 21, 2014, at 9:56 AM, Lucas Eznarriaga
Hi,
Below are the set of steps we are using for Jenkins setup and would like
some clarifications reg some of the steps.
Under Jenkins/Configure
1. Source Code Management: to be git and point to the devstack URL
2. Build Triggers: Gerrit Event
3. Build/Execute Shell: Sequence of
