Our 4th conference talk for TestBash Home is âReverse-engineer Your Way to Adopting a Risk-based Testing Approachâ with the lovely @testwithnishi.
Risk is such a key part of software testing and development but sometimes it can be difficult to define or prioritise. It will be really interesting to see Nishiâs approach to this
Weâll be adding all unanswered questions from the talk here so if we didnât get to your question, donât worry, we will find you an answer
If youâve got a question youâd like to ask in advance, why not ask it now?
Unanswered questions
- Nathan Owen: When do you determine the likelihood and impact analysis? It seems like it should inform plans for development as well as testing.
- atiqah azlan: Should we consider ambiguous or more clarification needed storypoints and dependecies that one feature have with another as risk?
- Ludmilla Chellemben: how long does it take to do risk analysis? Do u do it in all sprints? Do u have time for that? (partly answered. do u have teamâs resistance?)
- urvashi: How deep Domain knowledge is valid/required while doing Risk based testing?
- Sandy H: How would you carry out risk analysis if you donât use SCRUM? How would you plan risk based testing for a methodology such as Kanban, where work development is continuous rather than in sprints?
- Rob: How do you deal with a combination of Acceptance Criteria & Risks? Both need testing.
- Santiago: how do you factor in customer specific risk requirements? In one of your examples, localization had a low risk. But for a customer in that locale, that risk level would factor much higher.
- Beth: Your analysis metrics of existing stories included defects found in - and out of - sprint. You assigned an âOpportunityâ level testing for an area that actually had the highest number of defects found. Does this metric in itself not imply that the additional test effort was warranted rather than an âOpportunityâ approach which would have released these defects out?
- Imma: What kind of areas did you prioritize higher after implementing Risk-Based-Testing than before?
- PD: is this risk based approach for testers or developers, because of the rating do developers change their development approach