Why You Should Try Testing First - Nate Oster STARWEST2012 Lightning Keynote

1,062 views
891 views

Published on

Slides from the STARWEST2012 Lightning Keynote "Why You Should Try Testing First" (Nate Oster). This was a 5 minute time-boxed "lightning talk" moderated by Lee Copeland.

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,062
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
7
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Why You Should Try Testing First - Nate Oster STARWEST2012 Lightning Keynote

  1. 1. Licensed under a Creative Commons Attribution-NoDerivs 3.0 Unported License Why you should try Testing First… Nate Oster STARWEST 2012 nateoster@codesquads.com @nateoster
  2. 2. ACCEPTANCETEST-DRIVENDEVELOPMENT NateOster@CodeSquads.com
  3. 3. Great Reasons!• It kills werewolves.• All the cool kids are doing it.• It’s part of this balanced breakfast.• Superhuman strength. NateOster@CodeSquads.com
  4. 4. Waterfall Testing Release!DEV TEST NateOster@CodeSquads.com
  5. 5. Waterfall Testing Late!DEV TEST BUG-FIX NateOster@CodeSquads.com
  6. 6. Old habits die hard SPRINTS TEST NateOster@CodeSquads.com
  7. 7. Agile Means Incremental Testing SPRINTS NateOster@CodeSquads.com
  8. 8. Mini-Waterfall Testing 2 week sprint DEVSprint Planning Retrospective Sprint Demo TEST NateOster@CodeSquads.com
  9. 9. Mini-Waterfall Testing 2 week sprint DEVSprint Planning Retrospective Sprint Demo TEST NateOster@CodeSquads.com
  10. 10. Backpressure! 2 week sprint DEVSprint Planning Retrospective Sprint Demo TEST NateOster@CodeSquads.com
  11. 11. Micro-Waterfall Micro-Incremental Testing 2 week sprint Define Define Define Build Test Build Test Build TestSprint Planning Retrospective Sprint Planning… Sprint Demo Define Define Build Test Build Test Define Define Define Build Test Build Test Build Test NateOster@CodeSquads.com
  12. 12. Could we test first? fail fast? NateOster@CodeSquads.com
  13. 13. ACCEPTANCE TEST Yellow Refactor Red Green NateOster@CodeSquads.com
  14. 14. Verification Specification NateOster@CodeSquads.com
  15. 15. DEFINEEXAMPLESUSE CONCRETE DONE. REDUCE GUESSINGSTOP GOLD-PLATING DO LESS.GET FAST FEEDBACK. FINISH OFTEN CHANGE QUICKLYBE CLEAR. FOCUS ON ESSENTIALS NateOster@CodeSquads.com
  16. 16. rework velocityscrap feedbackhandoffs confidence NateOster@CodeSquads.com
  17. 17. Craft a Test-First Experiment Start small Hypothesize the outcome Get fast feedback Ask WHY. NateOster@CodeSquads.com
  18. 18. Licensed under a Creative Commons Attribution-NoDerivs 3.0 Unported License You can test first. Nate Oster STARWEST 2012 nateoster@codesquads.com @nateoster

×