Open Stack

On Thu, Feb 14, 2013 at 5:33 AM, Attila Fazekas <afazekas at redhat.com> wrote:

> Very good idea!
>
> I think it can fit into tempest repository,  but in a different directory.
>
> I would extend a scope too.


> At the first Round:
> - *mange command tests.
>

At first I was thinking of testing only testing the python-*clients, but
testing the *-manage CLI tools makes sense as well.


> - remote execution (with ssh connection pooling)
> The whitebox test type (not the existing test case), partially should be
> converted to utilities, partially the functionality should move to the new
> folder.
> https://github.com/openstack/tempest/blob/master/tempest/whitebox.py#L138


Agreed.

I am currently working on the first draft to get the new folder started, at
which point we can start moving thing around and expanding the tests.


>
>
>
> ----- Original Message -----
> > From: "Daryl Walleck" <daryl.walleck at RACKSPACE.COM>
> > To: "All Things QA." <openstack-qa at lists.openstack.org>
> > Sent: Thursday, February 14, 2013 3:33:20 AM
> > Subject: Re: [openstack-qa] New Client Test Suite
> >
> >
> >
> >
> >
> > We've bumped into some Novaclient only issues before in the past as
> > well. Sam and some of his team did prototype some tests that execute
> > using Novaclient. If there's any interest I can see about getting it
> > into a WIP branch to get eyes on it.
> >
> >
> >
> > Daryl
> >
> >
> > From: Joe Gordon [jogo at cloudscaling.com]
> > Sent: Tuesday, February 12, 2013 4:39 PM
> > To: openstack-qa at lists.openstack.org
> > Subject: [openstack-qa] New Client Test Suite
> >
> >
> >
> >
> > Hi All,
> >
> > We currently have thorough API tests (Tempest) that do an excellent
> > job of testing nova, glance, keystone, etc. But to date we don't
> > have anything that tests the assorted python clients.
> >
> >
> > Extensive python client tests, which would consist of mostly shell
> > commands, would prevent many bugs from arising such as:
> > https://bugs.launchpad.net/python-novaclient/+bug/1122958 .
> >
> >
> > The question is where should theses tests live?
> >
> >
> > * Devstack/smoketests - these are just smoketests and are not
> > designed to be exhaustive
> > * Tempest - currently explicitly doesn't use the python clients, but
> > we can add a separate folder that tests the clients
> > * In respective client repos - easier to require new tests when
> > adding to client, but will result in divergent test suites
> > * Separate Repo - perhaps this is premature?
> >
> >
> > I propose adding a separate folder in tempest to run the python
> > client tests, and taking it from there.
> >
> >
> >
> >
> > best,
> > Joe Gordon
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-qa/attachments/20130214/d005a59d/attachment.html>