I've been kicking around Django for a few months now and the one thing I've been trying to figure out is how to unit test my code. I understand how to go about testing the models (non-django provided functionality) and any other 'domain' objects I may have, but I'm struggling with how to test the views. More to the point, I'm wondering if testing views is worthwhile.
In building a few basic crud-ish apps it seems like the views are where most of the code is going to end up. Which means that's where most of the probems will end up. So, what I'd like to do is come up with a way to test that code. My idea is as follows: Write unit tests (preferably through doctest on the view functions) to test the contract established by the view. The contract is defined as what the view requires as input and what the view provides as output. Input would be GET/POST values, output would be the dictionary/context returned. The test might look something like this: >>> test_response = foo_view(foo_view_request) >>> len(test_response.context['foo_list']) 6 [ more tests here ] The two gotchas in this approach (and they're biggies) are where/how does foo_view_request get created/defined and how do I get the context onto the response object returned by the view (preferably in testing only)? If people deeper into projects than I am think this would be helpful or silly, please post and say so. I'm hoping to pick up some ideas on how to go about testing this code, or, if consensus says it's not really necessary, I may forgo it's testing... I thought I'd test the waters with this idea, so to speak... Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
