You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Santhosh Kumar Edukulla (JIRA)" <ji...@apache.org> on 2014/04/11 08:42:14 UTC

[jira] [Created] (CLOUDSTACK-6384) [Marvin]: Base.py and Service class changes

Santhosh Kumar Edukulla created CLOUDSTACK-6384:
---------------------------------------------------

             Summary: [Marvin]: Base.py and Service class changes
                 Key: CLOUDSTACK-6384
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6384
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: marvin
            Reporter: Santhosh Kumar Edukulla


1. Currently, the way base.py 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 base.py functionality, ideally it should abstract the base.py 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 base.py classes to have these parameters defined.
4. We can make the classes accept default keyword values defined from test_data, or services so that people can start using them in tests with out worrying much with creating, listing, using etc. EX: We will just say Network_obj.create(), rather passing complete argument list at times, if we can define keyword and mandatory arguments defined with initial default values to these apis, 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 little redundant. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)