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

There are several types of tests we could write for our application: units tests, integration tests, functional tests, smoke tests, and so on. We focus on the first three in this lesson.

## Unit tests
When building a test-driven web application in Django, each piece of functionality is individually tested. For example, maybe we implement a specific function to get particular data from the database. We can then write a test to make sure that the expected data is returned. This small test that tests a particular functionality of our application is called a __unit test__.

They’re called unit tests because they’re not meant to be comprehensive. They also don’t test the application as a whole but only test a particular functionality within the application.


There are several types of tests we could write for our application: units tests, integration tests, functional tests, smoke tests, and so on. We focus on the first three in this lesson.

# Unit tests
When building a test-driven web application in Django, each piece of functionality is individually tested. For example, maybe we implement a specific function to get particular data from the database. We can then write a test to make sure that the expected data is returned. This small test that tests a particular functionality of our application is called a __unit test__.

They’re called unit tests because they’re not meant to be comprehensive. They also don’t test the application as a whole but only test a particular functionality within the application.


Learn the difference between unit tests and integration tests.

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

Types of Tests

Unit tests