My presentation to PHP & Symfony User Group (January 31, 2014)

1. TDD – do increasing and save...

2. Who I am?
Programmer at Wargaming.net
~ 5 years php experience

3. Disclaimer

4. TDD - ?...

5. TDD this is...

6. ...or this?! Do you know it?

7. Expectations...

8. Reality...

9. Why not?...
TDD? And
who will
pay for it?
Good
thing! But
we
release
very soon
TDD does
not work
everywhere

10. Stress-free!
12
10
8
Plain
TDD
6
4
2
0
0
1
2
3
4
5
6
7

11. Why is that?...
- Start immediately
- Test First
- SOLID/Patterns
- Less coupled systems
- Stress control. Results are obvious
...

12. Test First...

13. SOLID
Single Responsibility
Open/Closed
Liskov Substitution
Interface Segregation
Dependency Inversion

14. Single Responsibility: Test
Data
- What does know?
- Relations between objects?
Behavior
- What problems resolve?
- Services?

15. Open/Closed: Test
- No need to change working code

16. Liskov Substitution: Test
- Tests can use to check the heirs instead ancestors
- In case of violation of unit tests are complicated

17. Interface Segregation: Test
- Tests help to split the interfaces
- Mocks dictates API

18. Dependency Inversion:TDD
- Service Locator or Dependency Injection?
- Mocks in TDD create abstractions
- Setting tests easier with Dependency Injection

19. TDD +/- Confidence in the code
to run
- No code to Thrash
- New solutions
approves more quickly
- New lever of your skills
- Slow refactoring
- Tests are difficult
- Doesn't work everywhere
- Tests refactoring
- TDD for bad smells code

20. FAQ...
- How many tests must be written?
- TDD for existing projects
- Must read

21. Books...
- Kent Beck "Test Driven Development By
Example"
- Martin Fowler "Refactoring: Improving the
Design of Existing Code"
- Joshua Kerievsky "Refactoring To Patterns"
- Michael Feathers "Working Effectively with
Legacy Code"

22. Questions?