On Tue, Oct 07, 2014 at 04:28:23PM +0100, Chris Dent wrote:
> On Mon, 25 Aug 2014, Joe Gordon wrote:
> >On Mon, Aug 4, 2014 at 3:29 AM, Chris Dent <chd...@redhat.com> wrote:
> >>For constraints: Will tempest be available as a stable library? Is using
> >>tempest (or other same library across all projects) a good or bad thing?
> >>Seems there's some disagreement on both of these.
> >
> >Yes, there is a separate thread on spinning out a tempest-lib (not sure on
> >what final name will be yet) that functional tests can use. Although I
> >think there is a lot  to be done before  needing the tempest-lib.
> 
> What's the status of tempest-lib? Looking at the repo it appears
> that other things may be taking priority at the moment.

Things were blocked briefly by global requirements freeze. I'll hopefully be
cutting the first release this week, just waiting on one patch to go through.
We already have most of the pieces in place already to start using it on ci 
jobs so it should just be a matter of getting: 
https://review.openstack.org/#/c/122478/ landed before you can import it
anywhere. That being said it's still a lower priority dev item compared to some
other tasks, mostly because we don't have too many interfaces in tempest which
are considered stable enough to migrate yet. The long term scope of the library
hasn't been clearly defined yest, so not entirely clear what things are worth
migrating into the library at this point. 

Next up I expect to migrate the auth layer and the base rest client. This will
allow projects to build service specific clients out of tree, which I've seen
commonly done for projects prior to incubation. This won't include the service
clients in tempest though, because we expect to make some changes to that
interface soon. That being said I'm not sure how long the additional library
migrations will take.

> 
> As I said in notifications thread: With summit approaching and kilo
> open for business, now seems to be talking about what kinds of
> structure we want to apply to in-tree functional testing.
> 

There is nothing stopping you from doing this. Tempest-lib is not a requirement
for doing this at all, and should really only be useful for some specific types
of testing. It shouldn't be required for functional testing in general. Also, at
this point tempest-lib only contains the CLI testing framework which is hardly
useful for spinning up project specific functional testing.

-Matt Treinish

Attachment: pgpHt8yHxOH3G.pgp
Description: PGP signature

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to