Your SlideShare is downloading. ×
  • Like
  • Save
Development without Testers: Myth or Real Option?
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Development without Testers: Myth or Real Option?

  • 4,460 views
Published

Presentation from XP Days Ukraine (December, 2011) and QADnepr Mini Conference (Dnepropetrovsk, October 2011) about true role of testers and ways to fix development process to avoid their …

Presentation from XP Days Ukraine (December, 2011) and QADnepr Mini Conference (Dnepropetrovsk, October 2011) about true role of testers and ways to fix development process to avoid their participation in usual stages of the quality control chain.

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
4,460
On SlideShare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
1
Comments
0
Likes
4

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. DEVELOPMENT WITHOUT TESTERS: MYTH OR REAL OPTION? Mikalai Alimenkou http://xpinjection.com 29.10.2011
  • 2. Background• Java Technical Lead/Scrum Master at Zoral Labs• 7+ years in software development• 5+ years of working by Agile methodologies• Expert in Agile engineering practices• Founder and coach at XP Injection (http://xpinjection.com)• Organizer of Selenium Camp, JEEConf and XP Days Ukraine conferences
  • 3. Before start doing something you need to understand it properlyI. WRONG VISION OF TESTINGACTIVITY
  • 4. Why so many testers?Too many bugs “Brave” automation team Endless regression testing Very quick development
  • 5. What is the “ideal” dev/tester ratio? Dev Tester ? Devs Tester ? Devs Tester ?X Devs Y Testers ?
  • 6. Where may problemshappen? Can’t implement what they want Can’t explain requirements Customer Existing functionality is Dev Team broken when new is ready
  • 7. Developer is the root of evil!
  • 8. Instead ofcontrollets fix it!
  • 9. People can’t read minds and any communication channels lose dataII. BROKEN REQUIREMENTSCHANNEL
  • 10. Divide work in small pieces
  • 11. Discuss everything in detailsbefore start implementing
  • 12. Use prototypes and mockups
  • 13. Make customers acceptresults of development responsibly
  • 14. Even very good developer can make stupid mistakeIII. DEVELOPERS MAKE MISTAKES
  • 15. Team design sessionbefore implementation
  • 16. 100% Code Review
  • 17. Pair programming for the most complex parts
  • 18. Detailed static code analysis
  • 19. Stable releasable trunk
  • 20. Strong definition of DONE Can I start testing this new feature? Yes, it is done! But I can’t even build the product… Ops, I forgot to commit some files...
  • 21. TDD at all levels ATDD TDDCustomer’s Tests Programmers’ Tests Acceptance Fixtures Production Unit Integration Tests Code Tests Tests
  • 22. Existing functionality must never be brokenIV. IMPLEMENTED ONCE, WORKINGFOREVER
  • 23. Build safety net fromcompletely automated tests
  • 24. Global Continuous Integration
  • 25. This role is always needed, but can be played by different peopleV. TESTER IS A ROLE, NOT A PERSON
  • 26. Magic happens when everybody know that there are no testers
  • 27. Team members canplay different roles
  • 28. Sharedresponsibility for quality is built
  • 29. Give development process what it really needsVI. HOW TO SURVIVE? PLAY RIGHTROLE!
  • 30. Help developers to do slicing development
  • 31. Perform muchexploratory testing
  • 32. Help customer toexpress his minds
  • 33. @xpinjection http://xpinjection.commikalai.alimenkou@xpinjection.com