In software development, having tests is essential.

As developers, tests not only help us sleep well at night, but they also allow us to iterate faster & make changes with more confidence.

If we want quality, we need tests.

When it comes to writing tests in Django, we often ask ourselves - “What to test?”.

It’s an important question since we don’t always have the time to test everything we want. Sometimes, we need to make a conscious decision about what to test & what to leave untested.

When making that decision, it’s important to have a good sense of “what’s important”, so we can test that.

Django gives us plenty of testing tools & a lot of choices for what to test - we can test models, forms, views, APIs, serializers, services, selectors, tasks & basically anything that’s well defined within the Django Framework.

In this talk, we’ll do 3 important things:

1. We’ll put our quality assurance hat on.
2. We’ll explore different real-life scenarios with Django apps.
3. And we’ll see how to approach testing in those scenarios, so we can test the things that matter!

By exploring those scenarios, we’ll also touch upon the following topics:

• Having a test plan.
• Naming conventions for our tests & test methods.
• Django test settings.
• Factories.
• Test speed & optimizations.

The talk is going to be practical & pragmatic, giving plenty of examples & references for a follow-up.

Video: https://youtu.be/PChaEAIsQls