Learn different testing approaches to break applications along with Exploratory and Risk Based Testing
Have you ever been in a situation where:
-Stakeholders come to you/your QA team and say “We have about 2 hours before we push the new version of the application into production. Could you do some high level acceptance tests and ensure our app is stable before we do it”. You have no idea where to start and what to do in these 2 hours.
-You/your QA team has 3 days for testing the new version of the application. You have all these test ideas but do not know which one to do first, how to prioritize your testing and what kind of vulnerabilities to look out for?
I was one such Tester, who was in the above situation many times. Based on my experience testing various desktop, mobile and headless applications for several years now, I started categorizing various defects I have found and realized; there are some common testing approaches you could follow to quickly find vulnerabilities in your applications.
To take this one step further, I did a lot of research on Session Based Exploratory Testing (SBET) and Risk Based Testing; and combined it with the power of pairing. In this session, you will learn different approaches to break applications through hands on exercises, mind maps and templates I have created through my experience, and pairing.