Tutorials Hut

Tutorials Hut

  • Testing Foundation

      Basics of Software Testing
       What is Software Testing?
       Objective of Testing
       Why is testing necessary?
       Common Terms used in Testing
       Verification Vs Validations
       QA Vs QC
       Debugging Vs Testing
       Seven Testing Principles
       SDLC Vs STLC
       Fundamentals of Test Process
       Software quality Factors
       Software Development Models
       Waterfall Model
       V models
       Iterative Model
       Test Levels
       Component Testing
       Integration Testing
       System Testing
       Acceptance Testing
       Strategies for Integration Testing
       Big Bang
       Stubs and Driver
       Top Down Testing
       Bottom Up Testing
       Test Types
       Functional Testing
       Non- Functional Testing
       Structural Testing
       Re-testing & Regression Testing
       Static AND Dynamic Techniques
       Static Technique
       Dynamic Technique
       Static Analysis by Tools
       White Box Techniques
       Statement Coverage Testing
       Branch Coverage Testing
       Decision Coverage Testing
       Path Coverage
       Black Box Techniques
       Equivalence Partitioning
       Boundary Value Analysis
       Decision Table testing
       State Transition testing
       Experience Based TestingTechniques
       Random Testing
       Exploratory Testing
       Error Guessing
       Functional Testing
       Integration Testing
       Unit Testing
       System Testing
       Smoke testing
       Sanity testing
       Regression Testing
       Usability Testing
       Security Testing
       User Acceptance Testing
       White Box & Black Box Testing
       Globalization & Localization Testing
       Non Functional Testing
       Compatibility testing
       Endurance testing
       Load testing
       Performance testing
       Recovery testing
       Scalability testing
       Stress testing
       Volume testing
       Test Planning and Estimation
       Test Planning
       Test Strategies Vs Test Plan
       Test Approaches
       Risk and Testing
       Product Risks
       Project Risks
       Defect Management
       Defect LifeCycle
       Severity Vs Priority



  • Risk based Testing | Product Risk and Project Risk

    This article is going to be a complete guide to learn Risk Based Testing in Software testing.

    • Risk can be defined as “the chance of an event, hazard, threat or situation occurring and resulting in undesirable consequences or a potential problem”
    • This Testing uses risk (re-)assessments to steer all phases of the test process, i.e., test planning, test design, test implementation, test execution and test evaluation.
    Risk Based Testing

    Threat:

    A specific event that may cause and undesirable event to occur

    Risk Management involves

        • Assess what may go wrong
        • Prioritise Risk and decide what needs to be addressed
        • Implement controls to address the issues. In this lesson we will look at Project Risks and Product Risks followed by Risk-based Testing 

    Types of Risk

      1. Product Risks
      2. Project Risk

    Product Risk in software testing

      • Failure areas of the software or system (risk to the quality of the product)
      • The risk involved in software or system, the possibility that software or system may fail to satisfy end user/consumers expectations is known as product risk
      • It is also called Quality risks

    Examples of Product Risks are:

      • Failure prone software delivered
      • Tight Schedules, that make people work in a rush and commit more mistakes.etc
      • Potential that software/hardware could cause harm to an individual, company or environment
      • Poor software characteristics like functionality, reliability, usability and performance
      • Poor data integrity and quality for example data migration issues, data conversion problems etc
      • Software that does not perform its intended functions
    Testing can usually mitigate product Risks.

    Project Risk in Software Testing

    A risk related to management and control of the project that surround the project’s capability to deliver its objectives

    We can broadly categories project risks as below

    1) Organisational factors:

        • Skills, training and staff shortages
        • Communication Problems
        • Personnel issues
        • Political issues

    2) Supplier issues

        • contractual issues
        • third party Failures

    3) Technical issues:

        • Requirements not clear
        • Quality of Design and Code
        • Constraints
        • Test environment unavailability

    Project Risk are usually managed in an Excel Sheet (or Google Docs Spreadsheet)

    For each risk below information is required

        1. Risk Name & Description
        2. Risk Index – calculated by multiplying its probability by its consequence
        3. Risk owner
        4. Date of relevance
        5. Prevention Actions
        6. Contingency Plans

















  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    Scroll to Top