Test-Driven Development: Rozbudowany samouczek (nieoficjalne tłumaczenie)

Przedmowa

Dedykacja

Podziękowania!

O przykładach kodu

1. Uwagi dla programistów języka C#
2. Uwagi dla programistów języka Java
3. Część 1: Same podstawy

Motywacja – pierwszy krok w uczeniu się TDD

1. Jakie jest TDD?
2. Zaczynajmy !

Niezbędne narzędzia

1. Test framework
2. Framework do mockowania
3. Generator wartości anonimizowanych
4. Podsumowanie

To nie (tylko) test

1. Kiedy test staje się czymś więcej
2. Testy w świecie programistów
3. Raczej specyfikacja niż zbiór testów
4. Różnice między “wykonywalnymi” specyfikacjami i tymi “tradycyjnymi”

Programowanie poprzedzone wymaganiem (Wymaganie-najpierw)

1. Po co pisać specyfikację po fakcie?
2. “Najpierw-test” oznacza patrzenie na niepowodzenie
3. “Test-Po” często kończy jako “Test-Nigdy”
4. “Test-Po” często prowadzi do ponownego projektowania
5. Podsumowanie

Poćwiczmy to, czego się właśnie nauczyliśmy

1. Pozwól mi opowiedzieć sobie historię
2. Akt 1: Samochód
3. Akt 2: Tytuł dla Klienta
4. Akt 3: Test-Driven Development
5. Epilog

Odnajdźmy się odrobinę

How to start?

1. Start with a good name
2. Start by filling the GIVEN-WHEN-THEN structure with the obvious
3. Start from the end
4. Start by invoking a method if you have one
5. Summary

How is TDD about analysis and what does “GIVEN-WHEN-THEN” mean?

1. Is there really a commonality between analysis and TDD?
2. Gherkin
3. TODO list… again!

What is the scope of a unit-level Statement in TDD?

1. Scope and level
2. On what level do we specify our software?
3. What should be the functional scope of a single Statement?
4. Failing to adhere to the three rules
5. How many assertions do I need?
6. Summary

Developing a TDD style and Constrained Non-Determinism

1. A style?
2. Principle: Tests As Specification
3. First technique: Anonymous Input
4. Second technique: Derived Values
5. Third technique: Distinct Generated Values
6. Fourth technique: Constant Specification
7. Summary of the example
8. Constrained non-determinism
9. Summary

Specifying functional boundaries and conditions

1. Sometimes, an anonymous value is not enough
2. Exceptions to the rule
3. Rules valid within boundaries
4. Combination of boundaries – ranges
5. Summary

Driving the implementation from Specification

1. Type the obvious implementation
2. Fake it (‘til you make it)
3. Triangulate
4. Summary
5. Part 2: Object-Oriented World
6. Status: pretty stable
7. Teaching one thing at a time

On Object Composability

1. Another task for Johnny and Benjamin
2. A Quick Retrospective

Telling, not asking

1. Contractors
2. A Quick Retrospective

The need for mock objects

1. Composability… again!

Why do we need composability?

1. Pre-object-oriented approaches
2. Object-oriented programming to the rescue!
3. The power of composition
4. Summary – are you still with me?

Web, messages and protocols

1. So, again, what does it mean to compose objects?
2. Alarms, again!
3. Summary

Composing a web of objects

1. Three important questions
2. 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)?

1. Receive as constructor parameter
2. Receive inside a message (i.e. as a method parameter)
3. Receive in response to a message (i.e. as method return value)
4. Receive as a registered observer

Where are objects composed?

1. Composition Root
2. Factories
3. Summary

Interfaces

1. Classes vs interfaces
2. Events/callbacks vs interfaces – few words on roles
3. Small interfaces

Protocols

1. Protocols exist
2. Protocol stability
3. Craft messages to reflect sender’s intention
4. Model interactions after the problem domain
5. Message recipients should be told what to do, instead of being asked for information
6. Most of the getters should be removed, return values should be avoided
7. Protocols should be small and abstract
8. Summary

Classes

1. Single Responsibility Principle
2. Static recipients
3. Summary

Object Composition as a Language

1. More readable composition root
2. Refactoring for readability
3. Composition as a language
4. The significance of a higher-level language
5. Some advice
6. Summary

Value Objects

1. What is a value?
2. Example: money and names

Value object anatomy

1. Class signature
2. Hidden data
3. Hidden constructor
4. String conversion methods
5. Equality members
6. The return of investment
7. Summary

Aspects of value objects design

1. Immutability
2. Handling of variability
3. Special values
4. Value types and Tell Don’t Ask
5. Summary
6. Part 3: TDD in Object-Oriented World
7. Status: under development

Mock Objects as a testing tool

1. A backing example
2. Interfaces
3. Protocols
4. Roles
5. Behaviors
6. Filling in the roles
7. Using a mock channel
8. Mocks as yet another context
9. Summary

Test-first using mock objects

1. How to start? – with mock objects
2. Responsibility and Responsibility
3. Channel and DataDispatch one more time
4. The first behavior
5. Second behavior – specifying an error
6. Summary

Test-driving at the input boundary

1. Fixing the ticket office
2. Initial objects
3. Bootstrap
4. Writing the first Statement
5. Summary

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

Test-driving at the input boundary - a retrospective

Mock objects as a design tool

1. Outside-in development
2. Worked example
3. Programming by intention
4. Responsibility-Driven Design
5. Specifying factories

What not to mock?

1. Internals
2. How to use value objects in Statements?
3. How to specify value objects?
4. Terminal nodes in object graph

Guidance of test smells

1. Long Statements
2. Lots of stubbing
3. Specifying private members
4. Mocking third party

Revisiting topics from chapter 1

1. Constrained non-determinism in OO world
2. Behavioral boundaries
3. Triangulation

Maintainable mock-based Statements

1. Setup and teardown

Refactoring mock code

1. Part 4: Application architecture

On stable/architectural boundaries

Ports and adapters

1. Physical separation of layers

What goes into application?

1. Application and other layers

What goes into ports?

1. Data transfer objects
2. Ports are not a layer
3. Part 5: TDD on application architecture level

Designing automation layer

1. Adapting screenplay pattern
2. Driver
3. Actors
4. Data builders

Further Reading

1. Motivation – the first step to learning TDD
2. The Essential Tools
3. Value Objects