[openstack-dev] [nova] novaclient functional test guidelines

Sean Dague sean at dague.net
Tue Feb 24 20:30:39 UTC 2015


On 02/24/2015 03:28 PM, Ed Leafe wrote:
> On Feb 24, 2015, at 1:49 PM, Sean Dague <sean at dague.net> wrote:
> 
>>> IMHO the CLI should have an option to returned raw JSON back instead of
>>> pretty tabled results as well.
>>
>> Um... isn't that just the API calls?
>>
>> I'm not sure creating a 3rd functional surface is really the answer
>> here, because we still need to actually test the CLI / pretty table output.
> 
> The python-openstacksdk project was originally envisioned to wrap the API calls and return usable Python objects. The nova client CLI (or any other CLI, for that matter) would then just provide the command line input parsing and output presentation. It's been a while since I was involved with that project, but it seems that decoupling the command line interface from the Python API wrapper would make testing much, much easier.

Right, I think to some degree novaclient is legacy code, and we should
focus on specific regressions and bugs without doing to much code change.

The future should be more focussed on openstacksdk and openstackclient.

	-Sean

-- 
Sean Dague
http://dague.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 465 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150224/3bf3b38f/attachment.pgp>


More information about the OpenStack-dev mailing list