> -----Original Message-----
> From: Prasanna Santhanam [mailto:[email protected]]
> Sent: Wednesday, June 06, 2012 1:43 AM
> To: [email protected]
> Subject: Re: bvt question
>
> On Wed, Jun 06, 2012 at 04:06:01AM -0400, kangta123 wrote:
> > hello ,
> > there are some problems when i using BVT test. I have
> successfully
> > deployed the bvt environment with Simulator host that simulate any
> resource
> > hosts, storages, network and so on. i can see zone, pod, cluster,
> host,
> > storage, ssvm on cloudstack dashboard . but when i test ssvm , it
> throws
> > error message "error: [Errno 110] Connection timed out".
> > i want to know if the simulator and BVT is ready for run , if i
> > missed any steps, please tell me
>
> Hello Kang -
>
> Thanks for your interest in the tests.
>
> The BVTs were written for live deployments. In this case the test is
> attempting to login to the SSVM and verify if the agent process
> inside it is functioning correctly. Since the simulator environment is
> entirely mock objects this check will fail.
>
> To have the BVT functioning for the simulator we have to strip it off
> of these kind of verifications. There are two ways to do this:
>
> 1> Prepare an alternate BVT set without the backend checks
> 2> Use the existing BVT and alter the test framework to skip backend
> checks for the simulated environment.
>
> 1> is easier to do, but will cause code duplication.
>
> 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?
>
> I'm open to any ideas that may help us port these tests quickly for
> the simulator.
>
>
> --
> Prasanna.,
