This is a document to help write tests using the new simulator mock framework.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Writing+tests+leveraging+the+simulator+enhancements

On 18-Apr-2014, at 5:09 PM, Koushik Das <koushik....@citrix.com> wrote:

> I have added this to master as part of commit 
> b088821c61c77fc7f7f4fa005f4f5fbbac2862f8.
> The following test scenarios are also added based on the new changes:
> - Deploy VM failure and retry logic due to volume creation failure.
> - Deploy VM failure and retry logic due to failure in starting VM.
> - User VM HA (host failure is simulated and CS moves HA enabled VM on another 
> host)
> 
> Try out these tests and let me know if there are any issues. Also running 
> them will help in understanding the simulator changes. Please leverage these 
> changes to add more test scenarios which wasn't possible earlier using 
> simulator.
> 
> 
> On 01-Apr-2014, at 5:47 PM, Koushik Das <koushik....@citrix.com> wrote:
> 
>> The current simulator provides a way to test various Cloudstack features 
>> without using actual resources. But its current capabilities are limited 
>> since it only allows success response for all agent commands and some 
>> ability to introduce delays. I am proposing some enhancements to the 
>> simulator [1] based on which test developers can write end-to-end tests for 
>> scenarios which were earlier not possible. Some examples would be VM 
>> deployment failure (due to storage/network failure), VM deployment retry 
>> logic, user VM HA etc.
>> 
>> In the current set of automation tests mostly positive scenarios are tested 
>> as it is very complex to test negative scenarios with real hardware. With 
>> the ability to simulate failure, negative scenarios can be tested in an 
>> effective manner. Negative test scenarios will also help in improving the 
>> overall code coverage of the tests.
>> 
>> Please share your feedback/comments.
>> 
>> Thanks,
>> Koushik
>> 
>> [1] 
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Simulator+enhancements
> 

Reply via email to