A proper "agile" workflow for distributed collaboration on a largeish
chunk of functionality should be as follows:
Feature developer:
* implement tests for the features to be added
* commit locally
* implement the features
* commit locally
* run the test suite iteratively, fixing whatever the tests indicate
needs fixing
* commit locally
* push your changes to GitHub or whatever other public code hosting
service is used for collaboration
Lieutenant:
* review changes, expecting that the tests pass
* pull changes from feature developer's repo to the "central" repo
* run the test suite
* push changes to the public code hosting service
Nice and clean -- in an ideal world. In real life, the humongous time
wasted on running the test suite causes a tiny impulse of frustration
to be transmitted between the neurons in the developer's brain on
every line where you read "run the test suite".
Let me bet -- every single Django developer, who runs the test suite
regularly, has felt discomfort thinking of the time he has to wait for
the suite to complete. Which means slight aversion regards running the
tests, which in turn, brings about that tests are run as a last resort
("doh, I have to run the tests"), not as the happy default path ("yay,
time to run the tests!").
What if we try to be nice to ourselves and get #8138 and something in
the lines of http://oebfare.com/blog/2008/mar/25/faster-django-test-suite/
into trunk ASAP, especially now that the dynamic workflow is really
gaining ground (both aggregates and model-validation is managed this
way)?
(Lessons learned while collaborating on model-validation with Honza.
Given a dual-core T5500 CPU, 2 GB RAM, Ubuntu and SQLite on a laptop,
the full test suite takes 1346.841s (22 minutes!) to complete on the
trunk.)
"Work with People’s Instincts, Not Against Them"-ly yours,
Mart Sõmermaa
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
