Test Driven Development - In search of concrete and useful feedback

Why does testing sounds so hard to be done? Don't you think that knowing what, and how to do something should be premisses to development? How TDD could help us? Let's meet with a concrete and useful feedback way to do things.

Transcript

1. TEST DRIVEN DEVELOPMENT */
   4&"3$)
   0'
   $0/$3&5&
   "/%
   64&'6-
   '&&%#"$,
   !IFMNFEFJSPT http://www.flickr.com/photos/21387694@N03/2108575053/
2. I’ve heard... that... ahnnnn...
3. there is no such thing as BUG ZERO!
4. there is no such thing as BUG ZERO! while he’d explained to me that I had to click all the buttons SAID BY A TESTER...
5. maybe... JUST DON’T BE SO EASY
6. stress test execution Gerry Weinberg less higher higher
7. Top Down Bottom up Test scenarios ... acceptance criteria ... 22 text box... 15 combo box...
8. Everybody has a plan until they get punched in the face “ Mike Tyson
9. What makes you fail testing?
10. ? communication attention time requirements changes dead lines
11. FOLLOW ATTACHED MAP!
12. now... is just go and GRAB the reasure?!?
13. confused little map ...
14. TDD Test-driven Development
15. TDD Test-driven Development Software development technique
16. red write a test that fails!
17. green make it go as fast as possible!
18. yellow then refactor even find that is good!
19. red green yellow is that all?
20. practices are vectors from where you are to where you can get -Vinícius Teles “ XP extreme programming
21. TDD Test-driven Development PRIMARY PRACTICE XP extreme programming
22. TDD Test-driven Development XP extreme programming Depend on the practical situation, on the context. but they tend to bring MANY BENEFITS
23. The only constant in a ftware project is change.
24. FEEDBACK!!!
25. YOUR DOCUMENTATION SCREAM ..
26. 1. Write your user story; 2. Detail acceptance criteria; 3. Copy the criteria for your test class; 4. Write the functional test for each criterion; 5. Stop when they are all going! [Lista de Ferramentas] Given... When... Then...
27. DESIGN how does your code evolves?!?
28. 1. Write your user story; 2. Detail acceptance criteria; 3. Copy the criteria for your test class; 4. Write the functional test for each criterion; 5. Stop when they are all going! [Lista de Ferramentas] Given... When... Then...
29. THANKS! Helio Medeiros - Grupo RBS @helmedeiros