> -----Original Message----- > From: Prasanna Santhanam [mailto:prasanna.santha...@citrix.com] > Sent: Thursday, June 07, 2012 5:11 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: bvt question > > On Wed, Jun 06, 2012 at 02:11:51PM -0400, Edison Su wrote: > > > For 2> I'm not sure how to get that going. The test code right now > is > > > free to use any library to perform these kind of backend checks. So > it > > > would be harder to have these tests skipped with a simple framework > > > fix. > > > > How about add another annotation on test case, such as > > @hypervisor("all-except-simulator"), means this specific test case > > can only be executed when the zone has real hypervisors? > > That would be nice to have. But then more than 50% of the tests > perform some or the other form of backend verification. So the > decorator
Here is the place we can hack: I assume you are using ssh login into backend system(hypervisor host, ssvm or whatever) to verify the result. Then we can add a filter in the remoteSSHClient, if the destination is a simulator host(or the host created on simulator, or just simply a global environment variable saying this deployment is only for simulator ), do nothing, just return "success". Will it work? > will run on too few tests. I've startd porting the tests to work on the > simulator so we can have a small jenkins job to start with that runs > against each checkin to begin with. > > Another idea that Chirag (@clogeny) discussed with me was adding tags > to test cases. So a test_port_forward_vm would be tagged with a list > of attributes like: > > def test_port_forward_vm(cloudstackTestCase): > ... > ... > tags = ['network','port forward', 'advanced', 'xenserver'] > > This way when I want to run all network tests I can identify and run > those. And then if I wanted to run xenserver tests I can do the same. > Or if it's only going to be an advanced zone I can filter those too. > > What do you think? > > > -- > Prasanna.,
