Test-Driven Development: Extensive Tutorial

Grzegorz Gałęzowski

Table of Contents

Front Matter

Dedications
Thanks!
About code examples
- Notes for C# users
- Notes for Java users

Part 1: Just the basics

Motivation – the first step to learning TDD
- What TDD feels like
- Let’s get it started!
The essential tools
It’s not (only) a test
Statement-first programming
Practicing what we have already learned
Sorting out the bits
How to start?
How is TDD about analysis and what does “GIVEN-WHEN-THEN” mean?
What is the scope of a unit-level Statement in TDD?
Developing a TDD style and Constrained Non-Determinism
Specifying functional boundaries and conditions
Driving the implementation from Specification

Part 2: Object-Oriented World

On Object Composability
- Another task for Johnny and Benjamin
- A Quick Retrospective
Telling, not asking
- Contractors
- A Quick Retrospective
The need for mock objects
- Composability… again!
Why do we need composability?
Web, messages and protocols
Composing a web of objects
- Three important questions
- A preview of all three answers
When are objects composed?
How does a sender obtain a reference to a recipient (i.e. how connections are made)?
Where are objects composed?
Interfaces
Protocols
Classes
Object Composition as a Language
Value Objects
- What is a value object?
- Example: money and names
Value object anatomy
Aspects of value objects design

Part 3: TDD in Object-Oriented World

Mock Objects as a testing tool
Test-first using mock objects
Test-driving at the input boundary
Test-driving at the input boundary – a retrospective
Test-driving object creation
Test-driving object creation – a retrospective
Test-driving application logic
- Summary
Test-driving value objects
Reaching the web of objects boundaries
What’s inside the object?
Design smells visible in the Specification
THIS IS ALL I HAVE FOR NOW. WHAT FOLLOWS IS RAW, UNORDERED MATERIAL THAT’S NOT YET READY TO BE CONSUMED AS PART OF THIS TUTORIAL
Mock objects as a design tool
- Responsibility-Driven Design
Guidance of test smells
Revisiting topics from chapter 1
Maintainable mock-based Statements
- Setup and teardown
Refactoring mock code

Part 4: Application architecture

On stable/architectural boundaries
Ports and adapters
- Physical separation of layers
What goes into application?
- Application and other layers
What goes into ports?
- Data transfer objects
- Ports are not a layer

Part 5: TDD on application architecture level

Designing automation layer
Further Reading

Notes

Test-Driven Development: Extensive Tutorial/Part 4: Application architecture/What goes into application?

What goes into application?

Application and other layers

Services, entities, interactors, domain etc. - how does it match?

Previous

Ports and adapters

Up next

What goes into ports?

In this chapter

What goes into application?
Application and other layers