I’m Lazy So I Write Tests

Does your team deal with bugs that could have been caught earlier in the development cycle? Wish you could get the benefits of Test-driven development (TDD) but are worried that your dev team might revolt or that stakeholders will think that you're being unproductive? In this talk, we'll discuss an approach I've taken to balance the concerns of developers and stakeholders while simultaneously increasing developer productivity, increasing knowledge sharing, and reducing software defects. I've named this approach "TBD", or "Test-backed development".

Transcript

1. I’M LAZY SO I WRITE TESTS
2. JAIME LOPEZ JR ▸ Past - iOS Lead at OfferUp ▸ Now - iOS Engineer at Simple ▸ @DevWithTheHair ▸ https://github.com/devwiththehair
3. I’M LAZY
4. SO I WRITE TESTS
5. ?
6. TDD
7. TEST-DRIVEN DEVELOPMENT
8. OBSTACLES
9. DEV TEAM
10. TOO TIME CONSUMING!
11. TEST CODE ISN’T *PRODUCTION* CODE!
12. WE’RE BEHIND SCHEDULE!
13. STAKEHOLDERS
14. TOO TIME CONSUMING!
15. TEST CODE ISN’T *PRODUCTION* CODE!
16. WE’RE BEHIND SCHEDULE!
17. WHAT TO DO?
18. TDD
19. TDD
20. TBD
21. TEST-BACKED DEVELOPMENT
22. EXAMPLES
23. API CALLS
24. SMOKE TESTS
25. DEMONSTRATE HOW SOMETHING WORKS
26. RESULTS?
27. DEV TEAM
28. STAKEHOLDERS
29. I’M LAZY
30. I’M LAZY
31. I’M BUSY
32. SO I WRITE TESTS
33. THANK YOU! @DevWithTheHair