Gain insights into test-driven development in Django, explore the differences between test methodologies, and learn to build robust applications through unit testing and Red-Green Refactor methodology.

django-docker.tar.gz

ALLOWED_HOSTS

steps involved in test-driven development

As Django co-founder Jacob Kaplan-Moss says, “code without tests is broken as designed.” That’s why it’s essential to develop your applications with tests and success conditions in mind.

This course is an introduction to test-driven development and a practical guide on applying these principles to Django development. You’ll start with the purpose of automated testing, including the differences between test-driven development and development-driven testing. You’ll then be introduced to Django, a Python framework for building web applications. You’ll design and write a series of unit tests before building a complete web application using Django—a web application that will pass all the tests you designed, to ensure a robust, low-risk experience.

By the end of this course, you’ll be familiar with test-driven development, Red-Green Refactor methodology, and deploying quality applications using Django.

Build Robust Applications with Test-driven Development in Django

To round up the e-library application, we’ll write tests for the views. The views will represent our application’s business logic. This means it serves as the code that receives a web request and sends a response back to the user. Here, there are two goals:

- The first is to enable the form to be able to save a new book to the database.
- The second is to display all the books to the users.

Currently, we just have the view that displays the empty form called `add_catalogue_form` in the `views.py` file.

## Write the test for the views

Let’s write some tests for the views:




To round up the e-library application, we’ll write tests for the views. The views will represent our application’s business logic. This means it serves as the code that receives a web request and sends a response back to the user. Here, there are two goals:

- The first is to enable the form to be able to save a new book to the database.
- The second is to display all the books to the users.

Currently, we just have the view that displays the empty form called `add_catalogue_form` in the `views.py` file.

# Write the test for the views

Let’s write some tests for the views:




Introduction

Steps Involved in Test-driven Development

E-library Application: Part One

E-library Application: Part Two

E-library Application: Part Three

What's Next?

Conclusion

Write and Run the Tests for the Views

Write the test for the views