django-responsediff 0.7.1 released

| by jpic | python django django-responsediff
This release includes a bugfix for the new feature added in 0.7.0, occuring with non-ascii characters in selector-based tests with python 2. Fix by @njoyard, test case by @jpic.

django-responsediff 0.7.0 release

| by jpic | python django django-responsediff
This new release includes: the possibility to filter content, contributed by @njoyard the possibility to crawl the website and test all pages

django-responsediff 0.3.0

| by jpic | python django best-practice django-responsediff
django-responsediff 0.3.0 has been released ! It now also checks the status_code, and has a cute mixin: from responsediff.test import ResponseDiffTestMixin class MixinTest(ResponseDiffTestMixin, test.TestCase): def test_admin(self): self.assertResponseDiffEmpty(test.Client().get('/admin/')) The above will fail on the first time with FixtureCreated to indicate that it has written responsediff/tests/response_fixtures/MixinTest.test_admin/{content,status_code}. This file is meant to be added to version control. So next time this will run, it will check that response.status_code and response.content is the same, in future version, or in other configurations (ie. Read More

Automatic fixtures for HTTP Response assertions

| by jpic | python django test django-responsediff best-practice
As stated in the “Database state assertion” article: I'm pretty lazy when it comes to writing tests for existing code, however, I'm even lazier when it comes to repetitive manual testing action. When my user tests my website, they browse it and check that everything is rendered fine. In the same fashion, django-responsediff eases doing the high-level assertions of page HTML rendering. Consider this example: class TestYourView(TestCase): def test_your_page(self): result = test. Read More
1 of 1