On 05/03/2012 03:54 PM, Daryl Walleck wrote:
So my first question is around this. So is the claim is that the client
tools are the default interface for the applications?
Sorry, perhaps a better term would have been the most common interface
to OpenStack Compute...
While that works
for
On 05/03/2012 10:54 PM, Maru Newby wrote:
The rest api is the default interface, and the client tools target that
interface. Since the clients are cli more than python api, they can be
used by any language that can use a shell. What exactly does
reimplementing the clients for the sake of testing
Walleck [daryl.wall...@rackspace.com]
Sent: Friday, May 04, 2012 12:03 AM
To: Maru Newby
Cc: Rick Lopez; openstack-qa-t...@lists.launchpad.net;
openstack@lists.launchpad.net
Subject: Re: [Openstack] [QA] Aligning smoke / acceptance / promotion
test efforts
Perhaps it's just me, but given if I
To: Maru Newby
Cc: Rick Lopez; openstack-qa-t...@lists.launchpad.net;
openstack@lists.launchpad.net
Subject: Re: [Openstack] [QA] Aligning smoke / acceptance / promotion
test efforts
Perhaps it's just me, but given if I was developing in a different language,
I would not want to use
] Aligning smoke / acceptance / promotion
test efforts
Perhaps it's just me, but given if I was developing in a different language, I
would not want to use a command line tool to interact with my application. What
is the point then of developing RESTful APIs if the primary client
+1 to this plan
From the above, I would surmise that smoke tests should have all three of
the following characteristics:
* Test basic operations of an API, usually in a specific order that makes
sense
as a bare-bones use case of the API
* Test only the correct action paths -- in other
=nttdata@lists.launchpad.net
[mailto:openstack-bounces+rohit.karajgi=nttdata@lists.launchpad.net] On
Behalf Of Daryl Walleck
Sent: Friday, May 04, 2012 1:24 AM
To: Jay Pipes
Cc: openstack-qa-t...@lists.launchpad.net; openstack@lists.launchpad.net
Subject: Re: [Openstack] [QA] Aligning smoke
So my first question is around this. So is the claim is that the client tools
are the default interface for the applications? While that works for coders in
python, what about people using other languages? Even then, there's no
guarantee that the clients in different languages are implemented
The rest api is the default interface, and the client tools target that
interface. Since the clients are cli more than python api, they can be used by
any language that can use a shell. What exactly does reimplementing the
clients for the sake of testing accomplish? Double the maintenance
Perhaps it's just me, but given if I was developing in a different language, I
would not want to use a command line tool to interact with my application. What
is the point then of developing RESTful APIs if the primary client is not it,
but these command line tools instead?
While it may appear
10 matches
Mail list logo
