Russell Keith-Magee wrote: > I've got a project at work that requires a formal test harness, so I thought > I would kill two birds with one stone and spend some time adding a formal > test framework for all Django applications.
Russell, that sounds great! It looks like everyone's reinventing the wheel here. Being a newbie in testing for python, it took me quite some time to put all the stuff together, especially with tests that require a test database. I can't comment much on the proposed structure, I'm now using py.test (but, hey, it really doesn't matter that much, and it's always a problem to include non-released software). It's probably very good that you include doctests AND unittests, it makes the life easy if you don't need the power of unittest. For my own project, I put together a testing middleware for views and manipulators, which saves the context given to a template and allows tests that are solely context based. The middleware can also write out test cases while you use the browser. I do this instead of selenium tests as long as I don't use Javascript. It doesn't depend too much on py.test. Please send me a mail if you're interested. Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
