cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-6384) [Marvin]: and Service class changes
Date Tue, 12 May 2015 12:05:28 GMT


Daan Hoogland updated CLOUDSTACK-6384:
    Fix Version/s:     (was: 4.5.1)

> [Marvin]: and Service class changes
> -------------------------------------------
>                 Key: CLOUDSTACK-6384
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: marvin
>            Reporter: Santhosh Kumar Edukulla
>             Fix For: 4.5.2
> 1. Currently, the way has been used especially with related to passing and using
services dictiionary is far confusing. 
> 2. Any change we do to services dictionary and its structure effects functionality,
ideally it should abstract the interfaces from internal data structures usage. 
> 3. We are not sure as which elements in services dictionary are mandatory and which are
not. This we can make sure to mention and use classes to have these parameters defined.
> 4. Writing test code in an easier fashion. We can make the classes accept default
keyword values defined from config\test_data, or services. Now, test suites can start using
them with out worrying much about the services\test_data while creating, listing, using etc.

> EX: We will just say 
> obj = Network()// Network class constructor will have keyword arguments defined with
default values or filled in from test_data.
> network_obj.create(),
> rather as we are doing now currently.
> EX: obj=Network(args)
> network_obj.create(args_again)
> Now, test writing need not worry much about services, then that should be good. 
> 5. This makes test writing cleaner and simpler. Lot places, we play around and shuffle
with services dictionary which is unwarranted. 

This message was sent by Atlassian JIRA

View raw message