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
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
d.net;
; Sam Danes
Subject: Re: [Openstack] [QA] Aligning "smoke" / "acceptance" / "promotion"
test efforts
Hi Tim,
I understand where you're coming from as well. I'm all for anything that gets
the job done right and keeps folks engaged. It's fair to
ounces+tim.simpson=rackspace@lists.launchpad.net>]
on behalf of Daryl Walleck
[daryl.wall...@rackspace.com<mailto:daryl.wall...@rackspace.com>]
Sent: Friday, May 04, 2012 12:03 AM
To: Maru Newby
Cc: Rick Lopez;
openstack-qa-t...@lists.launchpad.net<mailto:openstack-qa-t...@lists.launchpad
openstack-bounces+tim.simpson=rackspace@lists.launchpad.net
> [openstack-bounces+tim.simpson=rackspace@lists.launchpad.net] on behalf
> of Daryl Walleck [daryl.wall...@rackspace.com]
> Sent: Friday, May 04, 2012 12:03 AM
> To: Maru Newby
> Cc: Rick Lopez; openstack-qa-t...@lists.laun
ce@lists.launchpad.net] on behalf of
Daryl 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;
Subject: Re: [Openstack] [QA] Aligning "smoke" / "acceptance" / "promotion"
-Rohit
From: openstack-bounces+rohit.karajgi=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;
Subject: Re: [O
+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 o
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
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 eff
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 in
Hi all,
I'd like to get some alignment on the following:
1) The definition of what is a "smoke" test
2) How we envision the Tempest project's role in running such tests
First, a discussion on #1.
There seem to be very loose semantics used to describe what a "smoke
test" is. Some groups use th
12 matches
Mail list logo
