On Saturday, 15 February 2014 20:47:37 UTC+5:30, Chris Wilson wrote: > > Hi all, > > It just occurred to me that most classification systems are completely > arbitrary and therefore not very useful. What's a "system" test and how > would I know whether I need to run it? >
For development purposes we can stick to certain pre-defined and fixed categories. Users may define their own categories according to their own needs and wishes. But some ideas that I can think of that might be useful are: > > * Automatically building test coverage maps for each test, and reversing > them, so we can see which tests touch the line(s) of code that we just > modified, and rerun them easily. A good smoke test to run while modifying > part of Django. > py.test has a plugin for coverage reporting -> https://bitbucket.org/memedough/pytest-cov/overview. Might turn out to be helpful. > > * Categorising by imports: run all tests that import django.db or > django.core.http for example. Not perfect, some tests may touch facilities > without needing to actually import them, but it would be quick and cheap. > > This looks like another possible way we can go. > * Profile and speed up the test suite, so that we can run all tests more > quickly, especially with databases like postgres where it takes an hour to > run them all. > > Py.test -> we can parallelise and distribute test loads. -- 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/1edb3407-d3fa-4a82-8c0b-b33db2107c67%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
