openstack-qa-team team mailing list archive

[Jay Pipes <jaypipes@xxxxxxxxx>]

On 09/14/2012 06:51 AM, Jaroslav Henner wrote:
<snip>

> I think unittests may be relatively easily split between several Jenkins 
> jobs just by specifying which packages to run. Following might be 
> executed in different Jobs:
> 
> nose -w PATH_TO_TEMPEST tempest.tests.compute
> nose -w PATH_TO_TEMPEST tempest.tests.image
> nose -w PATH_TO_TEMPEST tempest.tests.network

True. The above granularity wouldn't be enough, of course, but we could
do it with something like:

nose tempest.tests.compute.test_servers
nose tempest.tests.compute.test_server_actions
etc, etc

> Have you guys considered DTests? https://github.com/klmitch/dtest
> 
> There is also Jenkins plugin that can distribute JUnit tests between 
> several workers. It would be great to have something same for Python 
> unittest/nose/whatever. Surely there would have to be some thinking done 
> about how to handle class/module fixtures.

Yes, I have, and we actually discussed DTest and PyVows yesterday at the
QA weekly IRC meeting. We are doing some prototyping from now until the
summit to see if there are better solutions. Very much welcome your
input and/or some example code from you!

Best,
-jay