What distinguishes preventive from reactive approaches?
Share
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Preventive Approach: This is a strategy used to avoid problems, also known as the verification process. Tests are created early in the software development lifecycle, prior to the software even being created. This strategy falls under the category of quality analysis, where testers attempt to stop faults in their tracks.
Reactive Strategy: Also referred to as the validation process, a reactive strategy is meant to find (or react) to flaws. The tests in this method are created to run after the software development, and it’s governed by Quality Control.