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.

Collaborative Exploratory and Unit testing -talk at Testival


Published on

Testing is about feedback. Working through the questions of what and how of testing, we’ve refined a tester-facing discipline of Exploratory testing and a developer-facing discipline of Unit Testing. We’ve built in-depth skills in those disciplines, their belief systems and their variations. We’ve brought specialists of each discipline to same teams to deliver software that is closer to ready for its stakeholders, together. In addition to understanding and valuing both the disciplines, we still need to mix the people of different disciplines with hands-on collaboration to harness the right insights of exploration to protect code. Cross-pollination of the two is needed for both sides to truly flourish.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Collaborative Exploratory and Unit testing -talk at Testival

  1. 1. Collaborative Exploratory and Unit Testing Maaret Pyhäjärvi Email: <> | Twitter: maaretpMaaret Pyhäjärvi & Llewellyn Falco Nimeä | Attribution (Finland)
  2. 2. A Course Experience in a Mob
  3. 3. How We Became How We Are
  4. 4. Testing as Performance (Exploring) vs. Testing as Artifact Creation
  5. 5. Certainty “I know what I know” Exploit Caution “I know what I don’t know” Explore Amnesia “I don’t know what I know” Expose Ignorance “I don’t know what I don’t know” Experiment Looking at World from Different Angles UnitTesting ExploratoryTesting
  6. 6. Testers don’t break your code, they break your illusions about the code. -- adapted from James Bach
  7. 7. What Testing Gives Us UnitTesting ExploratoryTesting SPEC FEEDBACK REGRESSION GRANULARITY GUIDANCE SERENDIPITY MODELS UNDERSTANDING Testing as artifact creation Testing as performanc e
  8. 8. A Few Ideas of Exploratory Testing • It’s not just about GUI and finalized features – You can explore an API – You can adapt to known limitations • It’s not just for functional – You should do exploratory performance testing • It’s not without automation – Sometimes you need to do things humans can’t do! – exploratory test automation • Repeating is seldom an issue – Vary the data, the environment, the story around your testing – exploratory regression testing
  9. 9. A Few Ideas of Unit Testing • There’s units of many sizes, really – Gravitating towards behaviors as units • It works great for expressing and recording intent – Spec, Feedback, Regression, Granularity! • There’s more than xUnit – E.g. ApprovalTests for more powerful asserts
  11. 11. 1st session on unit testing *
  12. 12. Strong Style Pairing “For an idea to go from your head to the computer it must go though someone else’s hands” *
  13. 13. Farming vs. Hunting
  14. 14. “Look at me” Pairing
  15. 15. Exploratory Testing
  16. 16. Why do this? “It’s about getting the best (not the most) out of everyone”
  17. 17. Quality
  18. 18. Quality
  19. 19. Quality Some devs care about testinPairing & Mobbing Remote desktop More powerful unit tests Some testers are great product owners MindMaps are amazing Skilled tester exist Testers don’t report everything
  20. 20. * That would’ve been a nasty one to find later
  21. 21. Thank you. @maaretp (please connect with me through Twitter or LinkedIn)