How TDD can be applied to Django Class based Generic Views?

前端 未结 3 1791
误落风尘
误落风尘 2021-02-02 10:13

Since Class based Generic Views in Django involve some work by the framework I find very hard to work with them in a TDD style. Now I use the TestClient to access the view from

相关标签:
3条回答
  • 2021-02-02 10:54

    Not sure if this is exactly what you're looking for, but this is an example of how I try to unit test my views (untested code below):

    import unittest
    from django.core.urlresolvers import reverse
    from django.test.client import RequestFactory
    from ..views import MyClassBasedView
    
    class MyClassBasedViewTestCase(unittest.TestCase):
    
        def setUp(self):
            self.factory = RequestFactory()
    
        def test_list_view(self):
            request = self.factory.get(reverse('your_url'))
            # additional params can go after request
            response = MyClassBasedView.as_view()(request)
            self.assertEqual(response.status_code, 200)
    

    I'd also recommend looking at the documentation that Filip mentioned in his answer.

    0 讨论(0)
  • 2021-02-02 10:57

    I was looking for a simple solution for the same issue today and found this really great blog-post by Benoît Bryon (thanks!).

    He suggested the following function:

    def setup_view(view, request, *args, **kwargs):
        """Mimic as_view() returned callable, but returns view instance.
    
        args and kwargs are the same you would pass to ``reverse()``
    
        """
        view.request = request
        view.args = args
        view.kwargs = kwargs
        return view
    

    Example

    I wanted to test the following CBV:

    class CreateList(CreateView):
        model = Item
        form_class = NewListForm
        template_name = 'lists/home_page.html'
    
        def form_valid(self, form):
            list_ = form.save(owner=self.request.user)
            return redirect(list_)
    

    The necessary tests are for the form.save method arguments and for the redirect arguments, which should be the return value of the former. These tests will look something like:

        class CreateListTest(unittest.TestCase):
    
            def setUp(self):
                self.request = HttpRequest()
                self.request.user = Mock()
                self.form = Mock()
                self.view = setup_view(views.CreateList(), self.request)
    
            def test_form_dot_save_called_with_user(self):
                self.view.form_valid(self.form)
                self.form.save.assert_called_once_with(owner=self.request.user)
    
            @patch('lists.views.redirect')
            def test_redirect(self, mock_redirect):
                self.view.form_valid(self.form)
                mock_redirect.assert_called_once_with(self.form.save.return_value)
    
    0 讨论(0)
  • 2021-02-02 11:05

    Generally, that would include creating a request via the RequestFactory and instantiating the view class with keyword arguments. Afterwards, you can call any of the view methods and evaluate the result, passing any required arguments.

    I'd recommend that you review the base View class, specifically the __init__, as_view and dispatch methods. They're crucial to understanding how the framework interacts with view objects.

    The most important bit to notice there is that view methods expect to be called during a request-response process, so they're allowed to rely upon self.request, self.args and self.kwargs to be present before they're called, so make sure you've got that covered.

    0 讨论(0)
提交回复
热议问题