QASymphony have kindly invited me to present a webinar for them entitled “Risk Mitigation Using Exploratory and Technical Testing”.
You can register to watch the webinar live. If you can’t make it, then register and you’ll be sent details of the free replay.
I’ve talked about Technical Testing and Exploratory Testing before. This time I want to approach it from the perspective of risk.
The blurb says:
“When we test our systems, we very often use business risk to prioritize and guide our testing. But there are so many more ways of modeling risk. If business risk is our only risk model then we ignore technology risks, and the risks that our processes themselves are adding to our project. Ignoring technical risk means that we don’t improve our technical skills to allow us to model, observe and manipulate our systems at deeper levels and we miss finding important non-obvious problems. Too often people mistakenly equate ‘technical testing’ with automating because they don’t model technical risk. In this webinar we’ll explain how to model risk and use that to push our testing further. We’ll also explain how to avoid some of the pitfalls people fall into while improving their technical testing.”
I’m still working out the details, but I think I’ll cover the following (and more):
- What do I mean by risk?
- Risks other than business risk.
- How to identify risk?
- Using risk to improve our process:
- What risk do our tools introduce?
- What risks does our process introduce?
- Risk mitigation
- What is technical risk?
- How to use this to drive my testing
- Risk as a coverage model
- Risk as a derivation model
Clearly I’m not using a statistical model of risk, or attempting to quantify it numerically. But I will be trying to explain how risk underpins the testing I conduct, and the processes I follow.
If I miss out any of the above for some reason, and you register,then you’ll be able to ask about the topic in the Q&A section.
Hope to see you there.