Clarification for testing docs

This is similar to my point above. At the moment, we have various different people:

* submitting patches, and stalling when it comes to tests
* wanting to write documentation *about* testing
* wanting to write some good practice guidelines and example django CMS applications

but finding themselves blocked because of difficulties presented by the test suite itself. We're in a vicious circle where the difficulties presented by the test suite > people avoiding it > people becoming less familiar and comfortable with it > the test suite become *unused* and *untried* > the test suite becomes more difficult to use

This is not going to change unless we offer some ways in to the test suite for people, even if some of them are only temporary work-arounds.

The issue does need to be solved, but it won't get solved if people run into brick walls and can't find ways around.