The document discusses different types of risks in testing including product risks, project risks, and ways to deal with risks. Product risks refer to risks that the software may not meet customer expectations or behave abnormally. Project risks relate to factors that could affect the test project delivery or environment. Both product and project risks should be identified early from requirements and previous projects. A risk mitigation plan is also needed to address potential risks like ensuring skilled resources, handling new defects, preparing for natural disasters, and resources leaving the project.

1. RISK & TESTING
http://appium-selenium.com/

2. RISKS AND LEVELS OF RISK
• It is possibility of some undesirable outcome
• The loss could be anything- money, time, effort or a compromise in
quality
• Also considering the consequences of that risk is also important
Example : Cold for young and old person may be having different
consequences i.e. risk likelihood and impact
http://appium-selenium.com/

3. PRODUCT RISKS
• Factors relating to what is produced by the work, i.e. the thing we
are testing
• Product risk refers we aren't able to deliver as per customer or
stakeholder expectations
• Software frequently behaving abnormally
• Software giving losses to customer
• Product risks should not be only due to functionality but rather
security, reliability, usability, maintainability or performance
• Risk bases techniques identify risk areas in beginning and using that
information during planning, design , implementation and execution
• Risk with Product are identified from requirement, meetings with
stakeholders and experts
• Previous similar Projects give risk areas while studying defects raised
http://appium-selenium.com/

4. PROJECT RISKS
• Factors relating to the way the work is carried out, i.e. the test project
• Factors relating to the way the work is carried out, i.e. the test project
direct risks such as the late delivery of the test items to the test team
or availability issues with the test environment
• Indirect risks such as excessive delays in repairing defects found in
testing or problems with getting professional system administration
support for the test environment
• Not enough resources, resources on boarding too late (process takes
around 15 days)
• Natural disasters
http://appium-selenium.com/

5. DEALING WITH RISKS, MITIGATION PLAN
Examples
1. Skilled Resources available
2. New defects
3. Natural disaster
4. Resources left
http://appium-selenium.com/

6. THANKS
http://appium-selenium.com/