On Sat, Aug 16, 2014 at 06:27:19PM +0200, Marc Koderer wrote: > Hi all, > > Am 15.08.2014 um 23:31 schrieb Jay Pipes <jaypi...@gmail.com>: > > > > I suggest that "tempest" should be the name of the import'able library, and > > that the integration tests themselves should be what is pulled out of the > > current Tempest repository, into their own repo called > > "openstack-integration-tests" or "os-integration-tests“. > > why not keeping it simple: > > tempest: importable test library > tempest-tests: all the test cases > > Simple, obvious and clear ;) >
While I agree that I like how this looks, and that it keeps things simple, I don't think it's too feasible. The problem is the tempest namespace is already kind of large and established. The libification effort, while reducing some of that, doesn't eliminate it completely. So what this ends meaning is that we'll have to do a rename for a large project in order to split certain functionality out into a smaller library. Which really doesn't seem like the best way to do it, because a rename is a considerable effort. Another wrinkle to consider is that the tempest namespace on pypi is already in use: https://pypi.python.org/pypi/Tempest so if we wanted to publish the library as tempest we'd need to figure out what to do about that. -Matt Treinish
pgpvUChCvCCKH.pgp
Description: PGP signature
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
