Hi all,
On Sat, 15 Feb 2014, Russell Keith-Magee wrote:
One of the improvements I see is classification of test cases.
Classifying them into categories (read multiple-categories), would make
it easier for users/developers/maintainers to run them. Basis of
classification,etc is what I am still thinking on. But surely
classification will help in deciding which all test cases to run. For
example - just running third-party app test cases, or just run my test
cases, or those which check part ABC of my project, or just those with
priority set to important.
[...]
I would envisage that this would be a declarative process - in code,
marking a specific test as a "system" test or an "integration" test (or
whatever other categories we develop).
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?
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.
* 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.
* 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.
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB1 2QF, UK
Aptivate is a not-for-profit company registered in England and Wales
with company number 04980791.
--
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/alpine.DEB.2.02.1402151512310.19498%40lap-x201.fen.aptivate.org.
For more options, visit https://groups.google.com/groups/opt_out.
