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

In this lesson, we continue to build the e-library application by adding tests for our Django application URLs.


## What are URLs?

The root of a website is usually mapped to a given domain name, which is mapped to an IP address. For example, *www.educative.io* is the main URL that navigates us to the root of the website (the home page). However, we can have several other URLs like the following:


- www.educative.io/courses
- www.educative.io/blog

These can be referred to as application level URLs. Inside this application, we can then have URLs for each view function or template, like so:

- www.educative.io/courses/test-driven-development-in-django

URLs are very important to an application and should be tested as well.

## The complete test for our URLs

Here’s the complete code that shows how we test the URLs for the e-library application:

In this lesson, we continue to build the e-library application by adding tests for our Django application URLs.


# What are URLs?

The root of a website is usually mapped to a given domain name, which is mapped to an IP address. For example, *www.educative.io* is the main URL that navigates us to the root of the website (the home page). However, we can have several other URLs like the following:


- www.educative.io/courses
- www.educative.io/blog

These can be referred to as application level URLs. Inside this application, we can then have URLs for each view function or template, like so:

- www.educative.io/courses/test-driven-development-in-django

URLs are very important to an application and should be tested as well.

# The complete test for our URLs

Here’s the complete code that shows how we test the URLs for the e-library application:

Learn to write and run the tests for the URLs.

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 URLs

What are URLs?

The complete test for our URLs