[TIP] Testify

Kumar McMillan kumar.mcmillan at gmail.com
Sat Oct 30 14:52:36 PDT 2010

On Fri, Oct 29, 2010 at 4:36 PM, Rhett Garber <rhettg at gmail.com> wrote:
>  * Split test suites into buckets for easy parallelization

Just like Holger, I too am very interested to hear about your approach
to splitting up test suites for running in parallel.  Nose has a model
for this but it's not very flexible.  py.test has a more flexible
model.  There are still a lot of challenges with running tests in
parallel and I think there is room for new ideas and strategies --
especially since most typical ways of writing tests in Python end up
sharing a lot of setup/teardown context which starts to make the
mechanics of parallel testing very difficult.  Parallel tests leads to
faster tests which leads to more productivity :)

That said, it would be a shame if there was another API split caused
by a new test runner.  For that reason I'd encourage you to read up on
Michael Foord's unittest2 work around formalizing a plugin API for
test suites.  There are threads in the archives here.  Nose and
py.test currently have a compatible plugin API (more or less) and this
allows some sharing of 3rd party plugins between the two tools.  Nose
also plans to be compatible with unittest2, not just for plugins but
so that Nose can evolve into a thin layer on top of unittest2.

And, yes, welcome to the list!  It's nice to see Yelp embracing the
open source community more.


More information about the testing-in-python mailing list