Download to read offline
Uploaded byHuib Schoots
Testing in modern times a story about quality and value - agile testing dev ops showcase 2020
The document discusses the importance of testing in software development, emphasizing that quality should be defined by the value it provides rather than just conformance to requirements. It advocates for a collaborative approach to learning and testing, where team members take responsibility for quality and use insights gained through exploration. Ultimately, the document suggests that organizations should focus on testability and integrate quality strategies based on risks, moving beyond traditional testing methods.
More Related Content
Similar to Testing in modern times a story about quality and value - agile testing dev ops showcase 2020
![[Paul Holland] Trends in Software Testing](https://cdn.slidesharecdn.com/ss_thumbnails/paulhollandtrendsinswtesting-140717230533-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Testing in modern times a story about quality and value - agile testing dev ops showcase 2020
- 1. Testing in moderntimes “a story about Quality and Value”
- 2. SoftwareDevelopment = R&D Research&Development
- 3. Research& Development: Dealing withunknownunknowns Capture everything upfront vs. building new insights Customers don’t know what they want Cope with complexity, confusion, change, new insights and halfanswers So: We need to learn and to deal with risks!
- 4. Testingand quality? Testing informsdecisions about quality & risk Quality isvalue to people who matter Quality is NOT: conformance to requirements Quality is NOT: the best product possible Quality products solve the problem and are “good enough”
- 5.
- 6. Business caseof LEARNING? Thequestion is: do you value learning?And if so: how much are you willingto pay? If you value it enough,you won'tdiscuss the price... But are thecosts justified? Or learn to live withoutit … withallrisks involved.
- 7. Reduce cost oftesting? Focuson Testability!
- 8. Reduce cost oftesting? Focuson Testability! Learnability (*) learning (*)Learnability: not the old ISO9126definition My definition: how easy is it tolearn about the value and risks of a product/solution
- 9. Testabilityyousay? Testability of aproduct is how easy it is to learn (read: test) by a particular team in a given context.
- 10. Learning about testability 10P’s of Testability Read more about this here: Team Guide to Software Testability - Better software through greater testability By Ash Winter and Rob Meaney (http://leanpub.com/softwaretestability)
- 11. Automate everything? Automated checksprovide binary answers to a question to which you already know the answer. We need a lot of checks to speed up development by detecting regression problems. Exploring can provide new insights into the product. Only people can provide this insight.
- 12. Can everybodytest? Sure. Thequestion is: how good do you want it to be? Most people do not like testing at all!And that is why they will never be good at it. Nor do they have time to learn these skills. We need smart people with "critical distance” to do skilled testing. People determined to find problems thatmatter. Problems asin: ”are there problems thatthreaten the value of the product or the on‐time successfuldelivery?” So are we stilltalkingabout testing? Or is it muchbroader?
- 13. About critical distance Weneed a diversity in thinking: different mindsets Opportunity mindset Solve problems Ask howand whenquestions Problem mindset Search for problems Ask what if questions
- 14. Learning in teams:it’s all about loops! Create learning loops (Plan-Do-Check-Act) in everything you do Team collaboration and skills are key: optimize your SDLC and processes Risks are a whole team responsibility Test your requirements & assumptions continuously Help programmers go faster: devand release pipelines, automated checks, codequality, measuring the right metrics Test enough (good is good enough): test & automation strategy! Oreven better: an integrated quality strategy based on risks Use tooling & automation in your exploration Mitigate “appropriate” risks by nottesting: monitoring, test in production, etc.
- 15. Learning in teams:it’s all about loops! Focus onfast learning in ourteams: Whole team quality! So are westilltalkingabout testing?
- 16.
- 17.
- 18. Referencesand more info Let’sstoptalking abouttesting,let’sstartthinking aboutvalue - http://www.huibschoots.nl/wordpress/?p=2763 Anne-MarieCharrett- Quality isaTeam Responsibility- https://youtu.be/mBC3ssLlJfQ Anne-MarieCharrett- ScrewTesting,Let’s Talk Quality - https://youtu.be/v4uw29pW73E TeamGuide toSoftwareTestability- http://leanpub.com/softwaretestability HeuristicsofSoftwareTestability - https://www.satisfice.com/download/heuristics-of-software-testability InterviewwithRob MeaneyonQualitycoachingroadshow- https://www.spreaker.com/show/quality-coaching TestabilityAsk Me Anything(Ash Winter) - https://www.ministryoftesting.com/dojo/lessons/testing-ask-me-anything-testability-ash-winter QualityEngineeringAsk me Anything (Anne-MarieCharrett)- https://www.ministryoftesting.com/dojo/series/testing-ask-me-anything/lessons/ask-me-anything-anne- marie-charrett-quality-engineering Rapidsoftwaretesting–https://www.rapid-software-testing.com Collectedlinks op mywebsite- http://www.huibschoots.nl/links
- 19. WhoamI? Context-drivensoftwaretester RapidSoftwareTestingteacher Scrummaster,team coach&agileexpert Humanist Curious& lifelonglearner Passionate&energeticpeoplelover Trainer,coach,consultant,writer,speaker Storyteller,leader,human,rebel,jiggler Trombone&guitar player,photographer,gamer, beer brewer,magician 2017 Most Influential Agile Testing Professional Person
- 20.
Editor's Notes
- #8 Automation = adding more unreliable code to the stack of code you already have….
- #9 Automation = adding more unreliable code to the stack of code you already have….
- #10 Automation = adding more unreliable code to the stack of code you already have….
- #11 Automation = adding more unreliable code to the stack of code you already have….