"all of the Windmill tests are run as a single Django test instance, meaning that they share the same test database and can potentially clobber one another's data. This is understandable, since the Windmill startup process is quite time-consuming, but it is contrary to the ideals of unit testing; each test is supposed to run in a completely independent environment. I worked around this using the following code instead of the example from the Windmill wiki:"
- Tom
"As the Cosmo client is heavy in JavaScript and AJAX functionality, Windmill makes the communication between the service and the client code a priority." Includes support for firing tests from Django test runner.
- Tom
If you're thinking of making a joke about an ark, 6 million other people have got you covered: http://twitter.com/#search...