>>> 3. 1 sec sleep and poll check is too heavy i believe, for async. So,
>> worst a test case can add time of execution by 5 seconds more, compared to
>> succesful operation time.
>>>
>>> Santhosh
>>> ____________________
>&
d I hope other people will religiously
> start using simulator/bvt (at least the basic ones) for their check-ins.
> >
> > Regards.
> >
> > On 01-Aug-2014, at 12:15 am, Edison Su wrote:
> >
> >>
> >>
> >>> -Original Message
14 7:15 PM
> To: dev@cloudstack.apache.org
> Subject: Re: How to speed up testing using BVT/smoke tests with Simulator
>
> Hi Edison,
>
> Thanks for the pointers! I’ll try them out and see if there is way to do it
> on Travis/CloudBees as well and I hope other people will religiously s
, Edison Su wrote:
>
>
>> -Original Message-
>> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
>> Sent: Thursday, July 31, 2014 5:12 AM
>> To: dev@cloudstack.apache.org
>> Subject: How to speed up testing using BVT/smoke tests with Simulator
&g
:
>
>
>> -Original Message-
>> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
>> Sent: Thursday, July 31, 2014 5:12 AM
>> To: dev@cloudstack.apache.org
>> Subject: How to speed up testing using BVT/smoke tests with Simulator
>>
>> Hi,
>&
> -Original Message-
> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
> Sent: Thursday, July 31, 2014 5:12 AM
> To: dev@cloudstack.apache.org
> Subject: How to speed up testing using BVT/smoke tests with Simulator
>
> Hi,
>
> Santosh put together
Hi,
Santosh put together a good wiki page on how to validate local changes using
our Python/marvin based build verification tests (path:
test/integration/smoke):
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Validating+check-ins+for+your+local+changes%2C+using+Simulator
I’ve a mini PC
