[openstack-dev] [Fuel] py.test vs testrepository
ikalnitsky at mirantis.com
Tue Oct 6 14:26:10 UTC 2015
> It’s ”standard" in OpenStack so using it gives Fuel more karma
> and moves it more under big tent
As far as I understand it doesn't affect our movement under big tent.
> It’s in global requirements, so it doesn’t cause dependency hell
Honestly I have no idea how py.test caused a dependency hell. It
almost doesn't have any dependencies:
* colorama for windows
* argparse for python 2.6 and 3.0
So the only possible intersection with global-requirements may is a
'py' package. Well, I checked and I didn't find 'py' package in there.
Summarizing, let's be practical - using py.test is convenient. It has
beautiful reports out-of-box, could be extended with a lot of
available plugins and so on. I'd prefer to keep it.
On Tue, Oct 6, 2015 at 2:14 PM, Yuriy Taraday <yorik.sar at gmail.com> wrote:
> On Mon, Oct 5, 2015 at 5:40 PM Roman Prykhodchenko <me at romcheg.me> wrote:
>> Atm I have the following pros. and cons. regarding testrepository:
>> 1. It’s ”standard" in OpenStack so using it gives Fuel more karma and
>> moves it more under big tent
> I don't think that big tent model aims at eliminating diversity of tools we
> use in our projects. A collection of web frameworks used in big tent is an
> example of that.
>> 2. It’s in global requirements, so it doesn’t cause dependency hell
> That can be solved by adding py.test to openstack/requirements.
>> 1. Debugging is really hard
> I'd say that debugging here is not the right term. Every aspect of
> developing with testr is harder than with py.test. py.test tends to just
> work where you need additional tools and effort with testr.
> In general I don't see any benefit the project can get from using testr
> while its limitations will bite developers at every turn.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev