On Wed, Oct 7, 2015 at 12:59 PM, Roman Prykhodchenko <m...@romcheg.me> wrote: > What I can extract now from this thread is that Fuel should switch to testr > because of the following reasons: > > - Diversity of tools is a bad idea on a project scale
We already have diversity about frameworks (or lack of them) in OpenStack. We have Pecan, Flask, wsgiref, Django. > - testrepository and related components are used in OpenStack Infra > environment for much more tasks than just running tests If by "more tasks" you mean parallel testing, py.test also has a possibility to do that by pytest-xdist. > - py.test won’t be added to global-requirements so there always be a chance > of another dependency hell As Igor Kalnitsky said, py.test doesn't have much requirements. https://github.com/pytest-dev/pytest/blob/master/setup.py#L58 It's only argparse, which already is in global requirements without any version pinned. > - Sticking to global requirements is an idea which is in the scope of > discussions around Fuel. > > Sounds like that’s the point when we should just file appropriate bugs and > use testr in smaller components, e. g., Fuel Client, first and then try in > in Nailgun. > > > - romcheg > Cheers, Michal __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
