1. If we want to collect all tests applicable for simulator, use nose test command below (just add these switches to existing nosecmd --collect-only --with-xunit --xunit-file=/tmp/x.xml ) It will dump all the tests under directory mentioned with -w switch and required_hardware=false(signifying simulator tests) to /tmp/x.xml file EX: /usr/local/bin/nosetests-2.7 -v --with-marvin --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml -a tags=advanced,required_hardware=false --zone=Sandbox-simulator --hypervisor=simulator -w test/integration/smoke --collect-only --with-xunit --xunit-file=/tmp/x.xml
2. Under smoke, we have misc directory they also get run as part of the above cmd, to exclude misc folder use --exclude-dir =<dir_pathto_miscfolder> to exclude that directory from running. This option is available with noseexclude plugin, check pip install noseexclude(something like that to install exclude plugin for nose) 3. Misc dir contains few tests, which are like interferring with other running tests, though they are written for simulator say to mock few behaviors, but to be run in sequentially not along with existing tests, if so you can exclude them, but if they are indeed failing even when run sequentially and are having required_hardware=false(simulator tests), then there indeed is a simulator mock approach problem or tests having issues. Santhosh ________________________________________ From: Ian Duffy [i...@ianduffy.ie] Sent: Thursday, September 04, 2014 8:19 AM To: CloudStack Dev Subject: Re: simulator run Koushik, Any chance of getting a list of tests that are valid for execution against the simulator for 4.3, 4.4 and master? Thanks, Ian On 4 September 2014 13:03, Koushik Das <koushik....@citrix.com> wrote: > Ok, in that case the tests under /misc won't get executed. Looks like > there are some other issues with the failing tests > > > grep required_hardware= test/integration/smoke/misc/*.py > test/integration/smoke/misc/test_deploy_vm.py: @attr(tags = > ['advanced'], required_hardware="simulator only") > test/integration/smoke/misc/test_deploy_vm.py: @attr(tags = > ['advanced'], required_hardware="simulator only") > test/integration/smoke/misc/test_vm_ha.py: @attr(tags = ['advanced'], > required_hardware="simulator only") > test/integration/smoke/misc/test_vm_sync.py: @attr(tags = ['advanced'], > required_hardware="simulator only") > > -----Original Message----- > From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers > Sent: Thursday, 4 September 2014 5:23 PM > To: dev@cloudstack.apache.org > Subject: Re: simulator run > > Hey, > > This is what i'm executing to run the tests: > > /usr/local/bin/nosetests-2.7 -v --with-marvin > --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml > -a tags=advanced,required_hardware=false --zone=Sandbox-simulator > --hypervisor=simulator -w test/integration/smoke > > > > Cheers, > > Hugo > > On 4 sep. 2014, at 13:32, Koushik Das <koushik....@citrix.com> wrote: > > > Are the tests present under test/integration/smoke/misc also getting > executed? If so please exclude them for now. > > The tests under /misc folder is based on the new simulator changes to > test failures from agent layer. These tests can cause interference in other > tests. > > > > There are 2 options to make them work together: > > - Run tests under /misc folder separately and in sequence > > - All existing smoke tests needs to be modified to run against some > targeted host(s). So that there is no interference from agent layer > simulated failures (these tests can target some specific hosts that are not > used by any other tests). > > > > -----Original Message----- > > From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers > > Sent: Thursday, 4 September 2014 1:09 PM > > To: <dev@cloudstack.apache.org> > > Subject: simulator run > > > > Heya, > > > > The simulator run reports three errors at the moment: > > > > integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_v > > m integration.smoke.test_network.TestReleaseIP.test_releaseIP > > integration.smoke.test_network.TestDeleteAccount.test_delete_account > > > > Can somebody with a bit of background on these tests do the > investigation? I'm happy to help with fixing the issue, but i can't really > figure it out atm. > > > > > > Cheers, > > > > Hugo > > > > > > > > > >
