[openstack-dev] [Fuel] py.test vs testrepository

Monty Taylor mordred at inaugust.com
Tue Oct 6 21:47:55 UTC 2015

On 10/06/2015 10:52 AM, Sebastian Kalinowski wrote:
> I've already wrote in the review that caused this thread that I do not want
> to blindly follow rules for using one or another. We should always consider
> technical requirements. And I do not see a reason to leave py.test (and
> nobody
> show me such reason) and replace it with something else.


The reason is that testrepository is what OpenStack uses and as I 
understand it, Fuel wants to join the Big Tent.

The use of testr is documented in the Project Testing Interface:


There are many reasons for it, but in large part we are continually 
adding more and more tools to process subunit output across the board in 
the Gate. subunit2sql is an important one, as it will be feeding into 
expanded test result dashboards.

We also have zuul features in the pipeline to be able to watch the 
subunit streams in real time to respond more quickly to issues in test runs.

We also have standard job builders based around tox and testr. Having 
project divergence in this area is a non-starter when there are over 800 

In short, while I understand that this seems like an area where a 
project can do whatever it wants to, it really isn't. If it's causing 
you excessive pain, I recommend connecting with Robert on ways to make 
improvements to testrepository. Those improvements will also have the 
effect of improving life for the rest of OpenStack, which is also a 
great reason why we all use the same tools rather than foster an 
environment of per-project snowflakes.

> Additionally other folks showed that this is not a blocker for moving
> under big tent.

I apologize for any confusion that may have resulted from you being 
given erroneous information.

More information about the OpenStack-dev mailing list