Hi everybody,
many thanks for engaging in our Software Testing Clinic Session on “Identifying Risks”.
I had an absolute blast. Loved the diversity and relevance of the risks that were identified in the different groups looking at the BBC Homepage, and expanding on the techniques and test activities identified to explore those risks.
For more on the topic, continue the discussion here, or over at the Ministry of Testing Slack channel (Sing up).
Risk away!
Cheers,
karo
For some background reading:
risk-based testing approach
- Cem Kaner: Risk Based Testing
- James Bach: Heuristic Risk-Based Testing
- James Bach: Reinventing Testing: What is Integration Testing? (part 2)
- Jenny Bramble: Risk Based Testing Because You Can't Do EVERYTHING [video, Pro Dojo Subscribers only]
- Andy Glover (Cartoon Tester): Risk Based Testing
Prioritising Risk (Risk = Likelihood * Impact)
Resources & Techniques introduced
- Mike Talks: Oblique Testing
- aka: Brian Eno, Peter Schmidt: Oblique Strategies to help artists break through creative blocks
- similar approach: Rosie Sherry: A Field Guide to Mobile App Testing
-
TestSphere (esp. Quality Aspects)
- Ministry of Testing Store: TestSphere
- Marcel Gehlen: RiskStorming - Mapping Risks with TestSphere
- YouTube: How To Do Risk Based Software Testing Using TestSphere (video)
- Negative Internal Press Release (workshop format)
Software Testing Clinic
- Risks? (99 second introduction)
And the flipcharts of the evening: