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

ASF subversion and git services commented on CLOUDSTACK-9120:
-------------------------------------------------------------

Commit 70439589979e618bca97e2303141a7c8b28170fa in cloudstack's branch 
refs/heads/master from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7043958 ]

Merge pull request #1195 from ekholabs/refactor/smoke_tests-CLOUDSTACK-9120

CLOUDSTACK-9120 - As a Developer I want the new component tests to be moved 
into the smoke directoryThis PR only moves the tests I wrote form the 
```component``` to the ```smoke``` directory. Given the nature of the tests, 
the should be moved.

   - Those tests are doing a lot more than component tests would do. They 
require hardware and a lot of resources from real hypervisors.

I'm now running the five test files that were moved and will post results once 
they are done.

* pr/1195:
  CLOUDSTACK-9120 - Moves tests to the smoke directory

Signed-off-by: Daan Hoogland <[email protected]>


> As a Developer I want the new component tests to be moved into the smoke 
> directory
> ----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9120
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9120
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Wilder Rodrigues
>            Assignee: Wilder Rodrigues
>            Priority: Minor
>
> The following tests...
> component/test_routers_network_ops.py
> component/test_vpc_redundant.py
> component/test_router_dhcphosts.py
> component/test_routers_iptables_default_policy
> component/test_vpc_router_nics
> ... should be moved into the smoke directory due to their nature.



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

Reply via email to