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
15 lines
740 B
ReStructuredText
15 lines
740 B
ReStructuredText
Disruptive (or faults) test cases are used for testing that after inducing some critical
|
|
disruption to the operation of the cloud, the services can get back to the expected state
|
|
after a while. To execute them you can type::
|
|
|
|
tox -e faults
|
|
|
|
The faults induced by these test cases could be cloud nodes reboot,
|
|
OpenStack services restart, virtual machines migrations, etc.
|
|
|
|
Please note that while scenario test cases are being executed in parallel (to
|
|
speed up test case execution), disruptive test cases are only executed sequentially.
|
|
This is because the operations executed by such cases could break some functionality
|
|
for a short time and alter the regular state of the system which may be assumed by other
|
|
test cases to be executed.
|