Apresentação utilizada como base para treinamento de equipe com técnicas de Test Driven Development.

1. Test Driven Development
Diego Caxito

2. Changing Software Reason
1. Adding a feature
1. Fixing a bug
1. Improving the design
1. Optmize resource usage
Working Effectively With Legacy Code

3. Usual Flow
Build Code
Build App
Test Manually

4. at the time
Change can be paintfull

5. In software, when something is
painful, the way to reduce the pain is
to do it more frequently, not less
Continuous Delivery

6. Lean startup loop fundamental

7. Do push para a produção - Agile Brazil 2014

8. Type of Tests
Continuous Delivery

9. Test pyramid
Martin Fowler Bliki

10. Do push para a produção - Agile Brazil 2014

11. when someone begin with
automation

12. Software testing pattern Ice-cream Cone Anti-Pattern
Watirmelon.com

13. Diferent tests can be overlap
Pragmmatic not dogmatic TDD

14. Ideal
Watirmelon.com

15. Test pyramid
Martin Fowler Bliki

16. Unit Test

17. Unit test
“Unit tests is the idea that they are tests in isolation of
individual components of software.”

18. Good Unit Test
It should be automated and repeatable.
It should be easy to implement.
Once it’s written, it should remain for future use.
Anyone should be able to run it.
It should run at the push of a button.
It should run quickly.
The art of uniting testing

20. TDD

21. Baby steps

22. Como a prática de TDD influencia o projeto de
classes em sistemas orientados a objetos.
Como a prática de TDD influencia o projeto de classes em
sistemas orientados a objetos.

23. Hello world!!!!!

24. Jasmine
● describe
● it
● expect
○ toEqual
○ toBe
○ not
http://jasmine.github.io/

25. Exercise

26. Dojo

27. Mock
Mock roles, not objects!
● como testar seu projeto javascript com dependência
○ isolando-a

28. Obrigado!