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.

TDD for Testers Workshop

188 views

Published on

Slides to accompany the workshop on TDD in the context of Quality Assurance - what developers use TDD for, how to do TDD and what this means for QAs

Published in: Technology
  • Login to see the comments

  • Be the first to like this

TDD for Testers Workshop

  1. 1. Workshop code and requirements available here*: Test Driven Development For Testers *If you feel like coding along, it’s not required
  2. 2. Test Driven Development @SarahNUsher #AGILEOTB @Agileonthebeach For Testers Sarah Usher
  3. 3. Sarah From Johannesburg, South Africa Developer +/- 7 years Software Product Development is a Team Sport
  4. 4. recipe Quick dose of theory Splash of code Sprinkling of insights
  5. 5. Code First Write Logic Write Test Refactor
  6. 6. Code First Write Logic Write Test Refactor
  7. 7. test First Refactor Write Logic Write Test See Test Fail See Test Pass
  8. 8. , ?
  9. 9. Types of tests Unit and Integration Tests Developer TDD Acceptance Tests Acceptance TDD Developers Automated Testers / Business Analysts / Product People / Devs ? Automated or Manual
  10. 10. Types of tests End-to-End Tests through all layers Functional & non-functional tests at any layer
  11. 11. pipeline Automated acceptance Tests Environment Tests Source Control Build Unit and Integration Tests Systems Integration Manual User Acceptance Testing
  12. 12. , !
  13. 13. QA vs Dev use of tdd Devs QAs ? Write unit & integration tests to drive the design of code interfaces: Test Driven Design
  14. 14. Developers are very, very good at abstraction. If you give us half a problem, we'll come up with the whole solution. In fact, we're so good at this, we won't even notice that we've only got half the problem. We're "solution space" people. Our job is to solve problems. Testers, on the other hand, are "problem space" people. They're the ones who ask, "What about X? Or Y? Have you thought about Z?" They know how to break our code before we've even written it. If we're really nice to them, they'll tell us. Their job is to understand the problem backwards.
  15. 15. QA vs Dev in testing QAs • Upfront acceptance criteria ie. BEFORE any code is written – automated if possible (dependant on production code and test automation tooling in use) • Focused solely on the potential problems / user paths – can determine edge cases, unlikely but possible scenarios, etc… • Free to be creative and explore the software • Write tests for issues discovered by users
  16. 16. QA vs Dev in testing • Redundancy is not a bad thing but don’t repeat tests unnecessarily – more to clean up later • Be aware of different tools Both (ideally whole team)
  17. 17. QA vs Dev in testing • Redundancy is not a bad thing but don’t repeat tests unnecessarily – more to clean up later • Be aware of different tools ie: Put the right tests in the right places Both (ideally whole team)
  18. 18. ! @SarahNUsher #AGILEOTB @Agileonthebeach
  19. 19. Sources/Reading • https://www.quora.com/Why-does-Kent-Beck-refer-to-the- rediscovery-of-test-driven-development-Whats-the-history- of-test-driven-development-before-Kent-Becks-rediscovery • https://softwareengineering.stackexchange.com/questions/2 58311/if-we-have-tdd-and-bdd-why-do-we-need-qa- for/258316

×