Risk Mitigation Using Exploratory and Technical Testing
Risk Mitigation Using Exploratory & Technical Testing
Improve risk assessment, testing and prioritization
Take a dive into the importance of risk mitigation and ways to improve it through exploratory and technical testing.
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 explain how to model risk and use that to push our testing further. We also explain how to avoid some of the pitfalls people fall into while improving their technical testing. Don’t miss this opportunity to learn:
Watch the on-demand webinar now.
Alan Richardson has worked in Software Development with a testing perspective for over 20 years. He has worked as a programmer, tester, test manager and now works as an independent test consultant helping organizations improve their agility, technical skills and testing processes. Alan is the author of the books “Dear Evil Tester”, “Java For Testers” and “Selenium Simplified”; he has also created online training courses on technical web testing, Java and Selenium WebDriver. Alan blogs at eviltester.com, seleniumsimplified.com, and JavaForTesters.com; you can find information on his consultancy, training and conference talks at compendiumdev.co.uk. Follow him on twitter as @EvilTester.