Describe how to perform Risk Analysis during software testing.

While a test plan is being created, risks involved in testing the product are to be taken into consideration along with possibility of their occurrence and the damage they may cause along with solutions; if any. Detailed study of this is called as Risk Analysis.

Some of the risks could be:

New Hardware

New Technology

New Automation Tool

Sequence of code delivery

Availability of application test resources

Identify and describe the risk magnitude indicators: High, Medium and Low

High magnitude means the effect of the risk would be very high and non-tolerable. Company may face severe loss and its reputation is at risk. Must be tested.

Medium: tolerable but not desirable. Company may suffer financially but there is limited liability or loss of reputation. Should be tested.

Low: tolerable. Little or no external exposure. Little or no financial loss. Company’s reputation unaffected. Might be tested.

Three perspectives of Risk Assessment: Effect, Cause and Likelihood.

To assess risk by Effect, identify a condition, event or action and try to determine its impact.

To asses risk by Cause is opposite of by Effect. Begin by stating an undesirable event or condition and identify the set of events that could have permitted the condition to exist.

To asses risk by Likelihood is to determine the probability that a requirement will not be satisfied.