On Sunday, 16 February 2014 06:27:01 UTC+5:30, Josh Smeaton wrote: > > Just a few observations that I've had when running the test suite that may > be relevant. > > - There are lots and lots of different test modules that may be relevant > to a particular change, and some may not seem relevant until you run the > entire suite > - bug* modules are hard to classify without reading the tests or the ticket > - *_regress modules seem too complex, and should be folded back in to the > main test module > - Creating a new test module is not as easy as it could be. Basically, > copy another test module, and search/replace the fixtures (if they exist) > - Setup/Teardown can be quite expensive across a large number of tests. > Perhaps individual tests could be longer (which is bad practise, but > practical with respect to time) > - There are 13 individual admin test modules. Perhaps it'd be nicer to > have them all under a single admin module, with separate TestCases within. > This applies to other systems like the ORM. > - It'd be nice if test modules could be parallelised, to improve total run > time of the test suite > > I think that restructuring the modules could take the place of tagging or > classification in a naive kind of way, but does not allow marking two > systems as relevant. For example, the checks framework has tests relating > to the admin, which should be run alongside any admin tests, but wouldn't > necessarily live in the admin module. > This is exactly what I was saying. Grouping them into corresponding folders sure is a naive way of classification, but there could be tests which may belong to multiple categories. Even if it becomes a pain to classify existing tests, giving the option to do so, in future, will surely lead to more structured and logically separated tests.
> Would pytest help with any of the issues observed with the current test > suite? > It will surely help. With features such as parallelising tests, to distributing them to multiple machines and testing on multiple platforms at once, pytest seems to me like a good choice. Thanks for your comments. :) -- Akshay Jaggi -- 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/bb47d05f-95db-4c19-b703-782cc54604db%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
