3d04906a9f
So far, the Tobiko docs were duplicated in some places, different
(although duplicated), and some fragments were not relevant (or
outdated).
This patch refactors the run test cases part of Tobiko quick start
guide by modularizing the fragments ("spilling" fragments instead of
coping them), correcting typos, and deleting/updating irrelevant
information.
Change-Id: I685182cde8573e80ecaabe8216530b903df759e1
21 lines
611 B
ReStructuredText
21 lines
611 B
ReStructuredText
Scenario and disruptive test cases, which are being executed in a specific
|
|
sequence, could be used to uncover more issues with the cloud than disruptive
|
|
test cases alone.
|
|
|
|
- First ensure there are workloads properly running by running scenario test cases::
|
|
|
|
tox -e scenario
|
|
|
|
.. sidebar:: Note
|
|
|
|
As second step we may, instead, update or upgrade OpenStack nodes.
|
|
|
|
- Next we could execute disruptive test cases to "stress" the cloud::
|
|
|
|
tox -e faults
|
|
|
|
- Finally we might re-run scenario test cases to check that everything is still running
|
|
as expected::
|
|
|
|
TOBIKO_PREVENT_CREATE=yes tox -e scenario
|