Book Image

Building Django 2.0 Web Applications

By : Tom Aratyn
Book Image

Building Django 2.0 Web Applications

By: Tom Aratyn

Overview of this book

<p>This project-based guide will give you a sound understanding of Django 2.0 through three full-featured applications. It starts off by building a basic IMDB clone and adding users who can register, vote on their favorite movies, and upload associated pictures. You will learn how to use the votes that your users have cast to build a list of the top 10 movies. This book will also take you through deploying your app into a production environment using Docker containers hosted on the server in Amazon's Electric Computing Cloud (EC2). </p><p> </p><p>Next, you're going to build a Stack Overflow clone wherein registered users can ask and answer questions. You will learn how to enable a user asking a question to accept answers and mark them as useful. You will also learn how to add search functionality to help users find questions by using ElasticSearch. You'll discover ways to apply the principles of 12 factor apps while deploying Django on the most popular web server, Apache, with mod_wsgi. Lastly, you'll build a clone of MailChimp so users can send and create emails, and deploy it using AWS. </p><p> </p><p>Get set to take your basic Python skills to the next level with this comprehensive guide! </p><p></p>
Table of Contents (19 chapters)
Title Page
www.packtpub.com
Contributors
Preface
Index

Testing your API


APIs provide value to our users by letting them automate their interactions with our service. Naturally, DRF helps us automate testing our code as well.

DRF provides replacements for all the common Django tools we discussed in Chapter 8, Testing Answerly:

  • APIRequestFactory for Django's RequestFactory class
  • APIClient for Django's Client class
  • APITestCase for Django's TestCase class

APIRequestFactory and APIClient make it easier to send requests formatted for our API. For example, they provide an easy way to set credentials for a request that isn't relying on session-based authentication. Otherwise, the two classes serve the same purpose as their default Django equivalents.

TheAPITestCase class simply extends Django's TestCase class and replaces Django's Client with APIClient.

Let's take a look at an example that we can add to django/mailinglist/tests.py:

class ListMailingListsWithAPITestCase(APITestCase):

    def setUp(self):
        password = 'password'
        username = 'unit...