Should Testers use Risk-based Testing only during Regression or should they use it even in weekly QA builds?
Should Testers use Risk-based Testing only during Regression or should they only test important stuff even in weekly QA builds?
My question is that when Production release is approaching and QA team starts the formal "Regression" suite testing, Now, is that a great time to use risk-based techniques to guide test design or should we use Risk techniques , every time, during exploratory testing sessions, even if we are testing a NEW functionality in the product for the first time?
Also, what exactly is a "risk-based" testing technique?
Thanks for the answers in advance?
Testing is the process of evaluating a product by learning about it through exploration and experimentation, which includes to some degree: questioning, study, modeling, observation, inference, etc.
Therefore, the level of risk-based testing you will deep depends on the techniques you use to question, study, model... the product and what you want to understand about it.
Think of testing as a walk in an optimization algorithm: You use your heuristic (risk analysis) to walk towards the global optimum (a bug) - however, you may end up on a local optimum (a simple bug) - therefore, some degree of chaos (not follow the heuristic) is necessary to increase the changes of finding the global optimum (the important bugs).
Your heuristic will get better with familiarity with the product, so you can slowly rely on it more and more. While, at the beginning, it's more interested to go with more extensive strategies, trying to cover a lot of ground.