> > >> 1. Distributed testing (speed up, especially on multi-core machines), >> Line Coverage, etc using plugins >> >> How would this work? We still have shared resources like the database > where you can't just run 10 Test against in parallel. >
There is django plugin for py.test <https://github.com/pelme/pytest_django>exists, it is able to create separate DBs for each process. On Thursday, February 27, 2014 11:59:56 PM UTC+4, Florian Apolloner wrote: > > Hi Akshay, > > On Thursday, February 27, 2014 8:50:32 PM UTC+1, Akshay Jaggi wrote: >> >> *Why Py.Test?* (http://pytest.org) >> >> 1. Widely Used >> >> So is nose and unittest, you'll need to add a bit more info to such > statements. > >> >> 1. Better reporting >> >> Better how exactly? > >> >> 1. Distributed testing (speed up, especially on multi-core machines), >> Line Coverage, etc using plugins >> >> How would this work? We still have shared resources like the database > where you can't just run 10 Test against in parallel. > > Cheers, > Florian > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/17553c1f-ec24-401f-8b62-91d39f1fbe54%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
