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

As we know, Django follows the Model-View-Template model. For our models, we’ve written both the test and the code. We discussed the view and also the template. However, we haven’t yet created a complete test suite for the template. This is what this particular lesson will focus on.

> __Note:__ It’s an iterative process to program an application. We go to the next piece of functionality as one is programmed out.

This project's template is only a single file called `index.html` that was prepared in the previous session. This is where the code that users view on the web application's homepage is stored.

## Test the template

The whole test for our template is shown below. It also shows the numerous test methods we’ll use as we iterate through our codebase to ensure that the required output is visible on the home page:

As we know, Django follows the Model-View-Template model. For our models, we’ve written both the test and the code. We discussed the view and also the template. However, we haven’t yet created a complete test suite for the template. This is what this particular lesson will focus on.

> __Note:__ It’s an iterative process to program an application. We go to the next piece of functionality as one is programmed out.

This project's template is only a single file called `index.html` that was prepared in the previous session. This is where the code that users view on the web application's homepage is stored.

# Test the template

The whole test for our template is shown below. It also shows the numerous test methods we’ll use as we iterate through our codebase to ensure that the required output is visible on the home page:

Learn to write tests for templates in Django.

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 Templates

Test the template