vkmc · April 24, 2020 14:55
diff --git a/tempest-tips-tricks b/tempest-tips-tricks
 - tempest init <some-name> (this will create an environment).
 This is not actually needed (I noticed later) since Devstack set ups the Tempest environment
 for you in /opt/stack/tempest
 - tox -e genconfig. This will generate the config file for you and store it under etc/.
 Again, not needed for Devstack since it does it automatically and you can find the config
 file already generated in etc/. The only thing you need to modify there is the Manila
 section (copy paste the one you are using, which I assume is what we have on the gate, and that must be fine).
 - Check that tempest is seeing the plugin.
 For what I saw, you specified enable_plugin manila_tempest_plugin in local.conf,
 and that won't work because there is no Devstack plugin for manila_tempest_test project.
 So, if you cloned it, make sure it is installed (Devstack installs everything from source
 or from pip, nothing from packages; pip install -e . in manila_tempest_plugin dir should make it work).
 The thumb rule for tempest, always install them in the same environment where tempest is installed.
 If tempest is installed system-wide, install them systemwide;
 if in a virtualenv, install them in the same virtualenv.
 In the case of Devstack, tempest is installed system-wide.
 - Once you have this done, make sure it is installed by issuing "tempest list-plugins".You can double check by listing all tests... "tempest run -l". You should see manila listed there.
	- tempest init <some-name> (this will create an environment).
	This is not actually needed (I noticed later) since Devstack set ups the Tempest environment
	for you in /opt/stack/tempest
	- tox -e genconfig. This will generate the config file for you and store it under etc/.
	Again, not needed for Devstack since it does it automatically and you can find the config
	file already generated in etc/. The only thing you need to modify there is the Manila
	section (copy paste the one you are using, which I assume is what we have on the gate, and that must be fine).
	- Check that tempest is seeing the plugin.
	For what I saw, you specified enable_plugin manila_tempest_plugin in local.conf,
	and that won't work because there is no Devstack plugin for manila_tempest_test project.
	So, if you cloned it, make sure it is installed (Devstack installs everything from source
	or from pip, nothing from packages; pip install -e . in manila_tempest_plugin dir should make it work).
	The thumb rule for tempest, always install them in the same environment where tempest is installed.
	If tempest is installed system-wide, install them systemwide;
	if in a virtualenv, install them in the same virtualenv.
	In the case of Devstack, tempest is installed system-wide.
	- Once you have this done, make sure it is installed by issuing "tempest list-plugins".You can double check by listing all tests... "tempest run -l". You should see manila listed there.