Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Be More Salmon - Testbash

108 views

Published on

Slides from my "Be More Salmon" talk at Testbash Manchester.

This version really focuses on the "shared documents do not equal shared understanding" idea from Jeff Patton

Published in: Software
  • Be the first to comment

Be More Salmon - Testbash

  1. 1. Duncan Nisbet Software Testing Guide duncannisbet.co.uk @DuncNisbet
  2. 2. Why Salmon?
  3. 3. Context is King
  4. 4. Context is King _ICTIONARY
  5. 5. Context is King _ICTIONARY
  6. 6. Context is King _ICTIONARY
  7. 7. Context is King DICTIONARY
  8. 8. Context is King _ICTIONARY
  9. 9. Context is King _ICTIONARY
  10. 10. Context is King PICTIONARY
  11. 11. The argument… Shared documentation != Shared understanding
  12. 12. The argument… Shared documentation ≠ Shared understanding
  13. 13. The argument… Shared documentation <> Shared understanding
  14. 14. The argument… Shared documentation does not equal Shared understanding
  15. 15. Shareddocs Shared understanding
  16. 16. The argument… • Shared docs do not equal shared understanding • Misunderstanding results in incorrect assumptions • Incorrect assumptions result in an undesired product
  17. 17. The conclusion… • Testing is asking questions to squash assumptions • The earlier we ask questions, the sooner we can squash assumptions, provide fast feedback & have a greater chance of delivering the desired product first time
  18. 18. ?
  19. 19. ?
  20. 20. Expected (required system) Actual (delivered system) James Lyndsay’s #1 diagram of testing
  21. 21. Expected (required system) Actual (delivered system) James Lyndsay’s #1 diagram of testing
  22. 22. Expected (required system) Actual (delivered system) Test Driven Development Test First Development
  23. 23. Expected (required system) Actual (delivered system) Need BDD 3 Amigo sessions Frequent releases Small batches Test Driven Development Test First Development
  24. 24. Design Of Everyday Things – Donald Norman
  25. 25. Dream Requirements Design Build How can I test upstream?
  26. 26. Dream Requirements Design Build
  27. 27. Dream Requirements Design Build As a … I want … So that …
  28. 28. Dream Requirements Design • Question the product • Break illusions • Feedback information
  29. 29. Dream Requirements Build • Discuss testability • Understand the design patterns • Understand the implications
  30. 30. Dream Design Build • Discuss testability • Squash assumptions • Make the implicit explicit
  31. 31. Requirements Design Build • Question the idea of the product • Understand the need • Understand the why
  32. 32. Dream Requirements Design Build Dream Requirements Design Build
  33. 33. Dream Requirements Design Build
  34. 34. Dream Requirements Design Build Dream Requirements Design Build
  35. 35. Dream Requirements Design Build Dream Requirements Design Build Dream Requirements Design Build
  36. 36. Dream Requirements Design Build Dream Requirements Design Build Dream Requirements Design Build Dream Requirements Design Build
  37. 37. Dream Requirements Design Build Dream Requirements Design Build Dream Requirements Design Build Dream Requirements Design Build Dream Requirements Design Build
  38. 38. Understand
  39. 39. Assumptions
  40. 40. Right Thing Thing Right
  41. 41. Continuous
  42. 42. Shareddocs Shared understanding
  43. 43. END
  44. 44. Many thanks to: Leigh Rathbone & the SD gang, Chris Thacker, Dan Ashby, Ash Winter, Gwen Diagram, Mark Winteringham & of course Mrs Nisbet duncannisbet.co.uk @DuncNisbet Feedback : http://bit.ly/TestbashSalmon

×