Why you must use TDD now!

Stop wasting time on QA cycles. Learn how TDD's 'Red-Green-Refactor' cycle builds quality in from the start, preventing costly production bugs.

#1about 5 minutes

Introduction and overview of the TDD talk

The speaker introduces himself, his company Avanade, and outlines the structure of the talk on test-driven development.

#2about 1 minute

The challenges of traditional code-first development

Traditional development cycles where testing happens after implementation often lead to bugs slipping into production.

#3about 1 minute

What is test-driven development (TDD)

TDD is a software development process that converts requirements into test cases before writing the actual implementation code.

#4about 2 minutes

The core TDD workflow is red-green-refactor

The TDD process involves writing a failing test (red), writing just enough code to make it pass (green), and then cleaning up the code (refactor).

#5about 6 minutes

Live demo of writing a failing test first

A live coding demo begins by creating a .NET Web API project and writing a test for a health check endpoint that fails as expected.

#6about 2 minutes

Demo of making the first test pass

The demo shows how to write the minimal amount of code, including a controller and configuration, to make the initial health check test pass.

#7about 5 minutes

Demo of testing a calculator's add endpoint

The TDD process is applied to a calculator's add endpoint, starting with a simple test and then adding more test cases to expose flaws in a naive implementation.

#8about 4 minutes

Demo of fixing implementation using test feedback

By running multiple test cases, subtle bugs like incorrect parameter names are identified and fixed, ensuring the implementation meets all requirements.

#9about 4 minutes