This is an old revision of the document!
Procedure shall be independant from the installer. The procedure shall be performed on any of the installer.
TODO: shall we be more prescritive on the toloing environment (creation of the VM, installation of the tools)?
for release 1 we target the automation of the following tests
The default scenario are:
the first ones (authenticate, nova, cinder, glance, keystone, neutron, quotas, requests, tempest-do-not-run-against-production) can be re-used. However scenario shall be tuned especially for the bench
Note: during first manual launched on alpha Orange platform installed with opensteak installer, there were lots of errors (196) running Tempest scenario and some in Rally scenario (results to be analyzed)
Studies on the testcase shall be done
To be discussed with CI team asap
|"Experiment"||#1 - "Foreman-Quickstack"||#2 "Fuel"||#3 "OpenSteak"||#4 "SlapStick"||#5 "Juju"|
|Installation of tools||Rally natively integrated in Fuel||Rally installed manually on a de dedicated tooling VM|
|Rally scenarios||Rally scenarios including tempest launched manually from the VM, see https://github.com/Orange-OpenSource/opnfv/blob/master/docs/TEST.md|
|Automation of scripts|