[
https://issues.apache.org/jira/browse/CLOUDSTACK-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416727#comment-15416727
]
Rajani Karuturi commented on CLOUDSTACK-9453:
---------------------------------------------
Hi Abhi,
Thanks for taking this up.
In the past, edison has done some work in moving nosetests to pytest and
claimed that it improved the speed arnd 10 times
([http://markmail.org/message/zawgslador2pkty2]). It never made it to the
mainstream branch but its in the pytest branch
([https://github.com/apache/cloudstack/tree/pytest]). Maybe it worth taking a
look.
Thanks,
Rajani
> 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
> Affects Versions: Future
> Reporter: Abhinandan Prateek
> Assignee: Abhinandan Prateek
> Fix For: Future
>
>
> 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)
