[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503031#comment-15503031
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9453:
--------------------------------------------

Github user abhinandanprateek commented on the issue:

    https://github.com/apache/cloudstack/pull/1639
  
    Thanks @karuturi @rhtyd 
    I created a new one for 4.8 here 
https://github.com/apache/cloudstack/pull/1675 @jburwell 


> Optimizing Marvin
> -----------------
>
>                 Key: CLOUDSTACK-9453
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9453
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: marvin
>            Reporter: Abhinandan Prateek
>            Assignee: Abhinandan Prateek
>             Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
>
> Currently running all Marvin tests can take upto 4 days. The tests are not 
> optimized for nested cloud setup where most of the test automation runs. 
> There are some simple things that can be done to optimize the runs:
> 1. Have smaller default template: If we install macchinina template by 
> default and use it where there is no specific dependency on OS, then it will 
> result in speeding up many of Marvin tests.
> 2. Most of the tests have template names hard-coded. It will be a good idea 
> to allow some form of configuration so that test writers can use templates 
> that better suit their test scenario.
> 3. Some test timeouts are unnecessary long and a failure can be deducted much 
> early on instead of undergoing several long timeouts.
> 4. Ability to tune service offerings to better suit marvin environments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to