Learn how to design and execute unit tests before building a complete application.

Become a Django Developer

This module is an introduction to test-driven development and a practical guide on applying these principles to Django development. We’ll start with learning about automated testing, including the differences between test-driven development and development-driven testing. We’ll then be introduced to Django, a Python framework for building web applications. We’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 we designed, to ensure a robust, low-risk experience.

By the end of this module, we’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

## Recap
That’s the end of the second chapter. Let’s have a short recap of what was covered and the key takeaways.

You were introduced to the five steps involved in test-driven development. These are as follows:

1. Write the test.
2. Run the test, and see it fail.
3. Write the actual code.
4. Make all tests pass.
5. Refactor the code using the underlying tests as a bedrock to make sure that the refactoring process doesn’t break anything.


>**Note:** The process of writing failing tests, writing code that makes those tests pass, and then refactoring the code to improve it is also called the **"Red, Green, Refactor"** process.

# Recap
That’s the end of the second chapter. Let’s have a short recap of what was covered and the key takeaways.

You were introduced to the five steps involved in test-driven development. These are as follows:

1. Write the test.
2. Run the test, and see it fail.
3. Write the actual code.
4. Make all tests pass.
5. Refactor the code using the underlying tests as a bedrock to make sure that the refactoring process doesn’t break anything.


>**Note:** The process of writing failing tests, writing code that makes those tests pass, and then refactoring the code to improve it is also called the **"Red, Green, Refactor"** process.

Here’s a short recap of what was covered in the second chapter.

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

Summary

Recap