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

  • What is Test Approach? Different Techniques and Types

    A test approach is the test strategy implementation of a project which defines how testing would be carried out, defines the strategy which needs to be implemented and executed, to carry out a particular task.

     Test approach has two techniques: 

        1. Proactive -tests are designed as early as possible in order to find and fix the defects.
        2. Reactive – test design comes after software or system has been produced

    Usually, Proactive test approach is followed. Proactive test approach and effective test strategy makes life easier of the tester.

    Through test approach, it is easy to identify:

        • What is the scope and objective of the testing process?
        • What needs to be considered and tested?
        • How to test?
        • How much to test?

    Typical approaches/strategies include:

    Test Approach in software testing
    1. Analytical

    • Focusing testing on the most critical functionality (risk based)
    1. Model-based

    • Stochastic or Monkey testing using random or statistical information (tool).Operational profiles
    1. Methodical approaches

    • Failure based (error guessing and fault attack) ,Experience-based
    •  check-list based and quality characteristic-based
    1. Process- or standard-compliant approaches

    • Industry-specific standards (Eg. medical, aviation)
    • Various agile methodologies
    1. Dynamic and heuristic approaches

    • such as exploratory testing (more reactive approach than pre-planned approach)
    • Execution and evaluation are concurrent tasks
    1. Consultative approaches

    • Test coverage is driven primarily by the advice and guidance of technology and/or business
    • domain experts outside the test team
    1. Regression-averse approaches

    • Includes reuse of existing test material, extensive automation of functional regression tests, and standard test suites

    Selecting a Test approaches/ strategy

    Approach is selected considering the context:

      • Risk of failure of the project, hazards to the product and
      • risks of product failure to humans, the environment and the company
      • Skills and experience of the people in the proposed
      • techniques, tools and methods
      • The objective of the testing endeavor and the mission of the testing team
      • Regulatory aspects, such as external and internal regulations for the development process
      • The nature of the product and the business
    Recommended Articles:

  • Leave a Reply

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

    Scroll to Top