Re: test driven development and mixin for views

Hi Arun, thanks for this advice. I finally came also to the conclusion that the best test would be to create (as part of each test case) all possible use case szenarios for this mixin class. For instance if it should be utilizable for ListView and CreateView then i would create unit tests again

Re: test driven development and mixin for views

Hi sassman, Since you mentioned TDD, I assume you are talking about unit tests. As with any matter in quality control, the more you can test, the better! In my opinion, you would need to provide atleast one testcase for each of the four CBV views. It is better to create a derived class in each

test driven development and mixin for views

Hi Folks, i recently wrote some small mixins that are intented to be attached to CBV like ListView, UpdateView, DetailView or even CreateView. The aim is to give users only access to their data. Their in terms of ownership. As an Example you have a Post model were a field called owner is a Fore