Thanks everyone for the clearance of the problem. I will remove the unit test's logic to check fir template, it seems a viable test case along with the status code value.
On Fri, Mar 29, 2019, 2:24 AM Chetan Ganji <ganji.chetan@gmail.com> wrote:
There is one more way you could do itclass TestIndexPageLoad(TestCase):def setUp(self):self.client = Client()self.response = self.client.get('/')def test_check_response(self):self.assertTemplateUsed(self.response, 'index.html')--On Fri, Mar 29, 2019 at 1:56 AM Chetan Ganji <ganji.chetan@gmail.com> wrote:I would prefer to just check the status code of the response object.This is what I have done. You have to check if it works for forms with csrf_token or not.class TestReverseUrls(TestCase):def setUp(self):self.client = Client()self.reverseUrls = ['index', 'login', 'register']self.response = {url:self.client.get(reverse(url)) for url in self.reverseUrls}def test_reverse_urls(self):for url in self.reverseUrls:self.assertEqual(self.response[url].status_code, 200)On Fri, Mar 29, 2019 at 12:57 AM Aldian Fazrihady <mobile@aldian.net> wrote:There are several things you can try:1. Mocking csrf token functions2. Passing the csrf token context from first HTML generation to the second HTML generation3. Wiping out the csrf token parts from both HTML before comparing them.--On Thu, 28 Mar 2019, 23:54 Simon Charette, <charette.s@gmail.com> wrote:--This is effectively failing because of a mechanism added in 1.10 to protectagainst BREACH attacks[0] by salting the CSRF token.I'm not aware of any way to disable this mechanism but testing against theexact HTML returned from a view seems fragile.I suggest you use assertContains[1] (with or without html=True) andassertTemplateUsed[2] instead.Cheers,Simon
Le jeudi 28 mars 2019 12:16:43 UTC-4, OnlineJudge95 a écrit :Hi people,I am following the book Test-Driven Development with Python by Harry J.W. Perceval. The book is using Django version 1.7 which is outdated as of now so I started with version 2.1.I am trying to unit test my index view. One unit-test that I have written is testing whether the index view returns correct HTML or not by comparing the input received throughthe unit-test fail with the following traceback
from django.shortcuts import render
# Create your views here.
def index(request):
if request.method == 'POST':
return HttpResponse(request.POST['item_text'])
return render(request, 'index.html')
lists/test.pyfrom django.http import HttpRequest
from django.template.loader import render_to_string
from django.test import TestCase
from django.urls import resolve
from lists.views import index
# Create your tests here.
class IndexViewTest(TestCase):
def test_root_url_resolves_to_home_page_view(self):
[...]
def test_index_view_returns_correct_html(self):
request = HttpRequest()
response = index(request)
actual_html = response.content.decode()
expected_html = render_to_string('index.html', request=request)
self.assertEqual(expected_html, actual_html)
def test_index_view_can_save_a_post_request(self):
[...]
requirements.txt
pytz==2018.9
selenium==3.141.0
urllib3==1.24.settings.py
# Application definition
INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'lists',
]
[...]Directory Structure
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/7f0f12be-fc3e-43c3-ba07-e48158def051%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAN7EoAb8Ov7GXZXV7Eao%3Dj_-w4bKKG75ebF0fnjbTzHO%2BxmB%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAMKMUjs28W%3Du-MEj4gUso_ffeK7JTz5EPRv9Qhbf4GdCA7%3DmAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAD%3DM5eQgDAxT%2BCCx6xtZpvHbx7Ny045tyBsGWN%3DQKzCsTYmu1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment