Hi Folks, I would like to know about the best practices followed for skipping tests not applicable for my environment. I know one of the ways is to use the below decorator over the test method: @test.skip_because(bug=BUG_ID) However, what if my deployment doesn't support VPNAAS and I want to
If the deployment does not support IPv6, we use the following convention to skip the tests at class level. https://github.com/openstack/tempest/blob/master/tempest/api/network/base.py#L65 Regards, --Sridhar. On 11/28/2014 01:50 PM, om prakash pandey wrote: Hi Folks, I would like to know
Thanks Sridhar. I'm aware of using skipException for skipping tests at class level. However, this involves putting it in every class to skip tests which are not desired. I was looking for a way to control the tests I want to run through some kind of a configuration file, the options to pass to
Tests can be skipped based on configuration file options. Its all depend on what all set of tests you want to skip for your environment. For example- to skip all sahara tests (as you mentioned) You can make config option - 'sahara' to false which will skip all sahara tests. Particular feature
On Mon, Nov 24, 2014 at 10:49:27AM +0100, Angelo Matarazzo wrote: Sorry for my previous message with wrong subject Hi all, By reading the tempest documentation page  a user can run tempest tests by using whether testr or run_tempest.sh or tox. What is the best practice? run_tempest.sh
Hi, Thanjs for clearing that up... I had a hard time understanding the screws before I went with testr. Regards, Vineet On 25 Nov 2014 17:46, Matthew Treinish mtrein...@kortar.org wrote: On Mon, Nov 24, 2014 at 10:49:27AM +0100, Angelo Matarazzo wrote: Sorry for my previous message with wrong
Hi, I cannot comment on the best practice. But I can point to you a few more methods and links. 1. https://dague.net//presentations/tempest-101/#/ 2. http://www.slideshare.net/kamesh001/open-stack-qa-and-tempest?next_slideshow=1 3.
Angelo, One more way to run Tempest is to run it via Rally. Rally will take care about installation, generating tempest.conf, running tempest, parsing storing output results. Here is manual: https://www.mirantis.com/blog/rally-openstack-tempest-testing-made-simpler/ As a bonus you'll get