Book Image

Becoming an Enterprise Django Developer

By : Michael Dinder
Book Image

Becoming an Enterprise Django Developer

By: Michael Dinder

Overview of this book

Django is a powerful framework but choosing the right add-ons that match the scale and scope of your enterprise projects can be tricky. This book will help you explore the multifarious options available for enterprise Django development. Countless organizations are already using Django and more migrating to it, unleashing the power of Python with many different packages and dependencies, including AI technologies. This practical guide will help you understand practices, blueprints, and design decisions to put Django to work the way you want it to. You’ll learn various ways in which data can be rendered onto a page and discover the power of Django for large-scale production applications. Starting with the basics of getting an enterprise project up and running, you'll get to grips with maintaining the project throughout its lifecycle while learning what the Django application lifecycle is. By the end of this book, you'll have learned how to build and deploy a Django project to the web and implement various components into the site.
Table of Contents (15 chapters)
1
Part 1 – Starting a Project
5
Part 2 – Django Components
10
Part 3 – Advanced Django Components

Testing Django REST API endpoints

This section will introduce writing test cases that test Django REST framework endpoints. When testing any REST API endpoints created using the Django REST framework, we need to use the APITestCase class provided by the rest_framework.test library. We also should use the APIClient() class provided by that same library when requiring authentication, instead of using the Client() class as we did before.

In the following exercises, we will create one test class that performs two tests: the first will create an engine object and the other will update an object.

Creating an object test case

This test will use the POST request method to send data to the http://localhost:8000/chapter-8/engines/ endpoint and create an engine object in the database. Since we are loading a data fixture that contains only two engine objects with the IDs 1 and 2, we should expect the new object to be created at index 3, but your results may vary. We will refer back to...