Learning about risk-based testing can give us a new approach to our testing challenges. Even though Risk-Based testing may ideally be a bigger undertaking, we can begin it by simply analyzing the product as well as each sprint for the impending risk areas and then following them through during test design and development, execution and reporting. I would like to share how I convinced my team about it by using their own case study, using our previous sprint’s data, defect counts based on user stories, and calculating risk priority numbers. I will also share an example of how you can adopt a simplistic, no-frills risk-based testing approach!
Nishi is a corporate trainer, an agile enthusiast, and a tester at heart! With 12+ years of industry experience, she currently works with Sahi Pro software as an Evangelist and Trainings Head. She is passionate about training, organizing testing community events and meetups, and has been a speaker at numerous testing events and conferences. Nishi is also a writer on technical topics of interest in the industry and has numerous articles published at numerous popular forums and her own blog https://testwithnishi.com/ where she writes about the latest topics in Agile and Testing domains.
- Linkedin- https://www.linkedin.com/in/nishi-g-02127aa/
- Twitter- https://twitter.com/testwithnishi