[openstack-qa] Refactoring Tempest service clients

Maru Newby marun at redhat.com
Mon Jul 1 15:55:43 UTC 2013



On Jul 1, 2013, at 11:45 AM, Daryl Walleck <daryl.walleck at RACKSPACE.COM> wrote:

> Based on my previous experiences, I have to advocate the opposite. My quick bullet point list about language bindings:
> 	• Are too helpful (re-tries, re-auth)
> 	• Hide specifics about the response from the tester
> 	• Stop the tester from manipulating a request in meaningful ways
> 	• Block the tester from injecting useful logging/timing of requests etc
> For simple, positive testing I can see the argument that language bindings provide a quick and dirty way to get started, but the downsides are too great for anything beyond basic smoke API testing.

If we are talking about doing this _properly_, it should be possible to generate bindings (both official and for testing) automatically from a machine-readable spec.  For all the negatives of something like WSDL, the alternative is surely worse.


m. 


> Daryl
> ________________________________________
> From: Monty Taylor [mordred at inaugust.com]
> Sent: Monday, July 01, 2013 9:15 AM
> To: openstack-qa at lists.openstack.org
> Subject: Re: [openstack-qa] Refactoring Tempest service clients
> 
> 
> I think that if you do this, you will wind up implementing a parallel
> set of client libraries.
> 
> I'm going to take this moment to advocate for just using the client
> libraries in tempest instead of direct HTTP, btw. 2 reasons - one - what
> Martina brings up - it's hard to write things with the direct HTTP. Two
> - we have integration testing for real at this point, whereas we did not
> have it when tempest was first written/designed. So the fact that the
> client libs are part of the gate should mitigate that.
> 
> But - as always- only my $0.02.
> 
> _______________________________________________
> openstack-qa mailing list
> openstack-qa at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa
> _______________________________________________
> openstack-qa mailing list
> openstack-qa at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa




More information about the openstack-qa mailing list