On Wed, Sep 5, 2012 at 7:46 AM, jyria <jyri...@gmail.com> wrote: > What is your experience? Is it worth it, and is it possible? > > I tried it and found it quite difficult to follow guideline of unit testing > -- testing a unit of code, a class for example. Maybe Im just ignorant, but > I didnt see, how can I create registration app only with unit tests. The > only way I could drive implementation with tests was using more like an > integration testing approach: calling requests with data and asserting that > new user was registered and that form was valid/invalid etc, but this goes > against TDD as I understand it. So should I not worry about pure "unit > testing" approach and use django client http request to validate > RegistrationForm. Or I should write unit tests for RegistrationForm class?
TDD is not unit-testing https://www.google.com/webhp?q=tdd%20is%20not%20unit%20testing in short, it's like you've found: the tests you easily get with TDD are more (but not exactly) like integration tests, because you test features, not units. The "test isolated units" mantra of unit-testing requires different work. There's nothing wrong in adding 'real' unit-tests, but it's not required to do effective TDD. I guess that since unittesting became so well known so long ago, almost all test frameworks (including Python's and Django's) call their base test class "UnitTest", but they're not; they're just tests. you make them feature tests, or integration tests, or unit tests, or whatever kind of test. now, about the pros/cons of unit-testing vs. other kinds of tests..... that's a whole debate that i'm not going to touch. -- Javier -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
