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

  • Test Plan in software Testing |Definition , Activities etc

    Test Plan is the most important activity undertaken by a test leader in any test project.

    This article will present you with a complete idea about TestPlan , Test Activities , entry and exit criteria etc.

    We will learn below topics in this article

    What is Test Plan?

      • It is the most important activity undertaken by a test leader in any test project.
      •  Ensures there is a list of tasks and milestones in a baseline plan to track progress .
      • Defines overall testing objectives and approach
      • Provides accurate test effort
    Test Plan

    Test Plan Activities

        • Determine the scope and risks that need testing, involve the Project Manager
        • Identify and agree on the objectives of testing, with a focus on TIME, QUALITY and COST.
        • A Test Strategy (Overall Approach) ensures that test levels, entry criteria and exit criteria are defined
        • Making decisions
          • Features to test?
          • What roles will perform the testing activities?
          • When and how the testing activities should be done?
          • How the test results will be evaluated?
          • Exit criteria
        • Create a Plan to identify when and who will undertake the test analysis and design activities along with the documentation of the schedule for test implementation, test execution and test evaluation
        • Decide on the format of test project documentation, and which plans and test cases will be documented.
        • Define Management information including the metrics required, establishing processes to monitor and control test preparation and execution along with defect resolution and risk issues.
        • Ensure that test documentation generates test assets i.e. test cases.


        • Defines when to start testing
        • Can include the start of a level of testing, start of test design and/or start of test execution.
        • The stages of Entry Criteria to Test Execution are as follows:
          • Test tools installed in the environment which should be ready for use.
          • Testable code is available.
          • All test data is available and correct.
          • All test design activity has completed.


        • Exit Criteria is used to decide when a test activity has been completed or needs to stop.
        • Exit Criteria can be defined for all test activities such as planning, specification and execution or for a specific test level for test specification and execution.
        • Exit Criteria should have been agreed as early as possible in the life cycle.

    Typical exit criteria are:

        • Estimates of defect density or reliability measures
        • Functionality or risk
        • Thoroughness measures, such as coverage of code,
        • Residual risks, such as defects not fixed or lack of test

    IEEE-829 Test Plan

      1. TestPlan Identifier
      2. References
      3. Introduction
      4. Test Items
      5. Software Risk Issues
      6. Features to be Tested
      7. Features not to be Tested
      8. Approach
      9. Item Pass/Fail Criteria
      10. Suspension Criteria and Resumption
      11. Requirements
      12. Test Deliverables
      13. Remaining Test Tasks
      14. Environmental Needs
      15. Staffing and Training Needs
      16. Responsibilities
      17. Schedule
      18. Planning Risks and Contingencies
      19. Approvals
      20. Glossary

    SPACE DIRT = IEEE829 TestPlan

    S – Scope test items, what to test, what not to test

    P – People training, responsibilities, schedule

    A – Approach the approach that will be taken to testing

    C – Criteria entry/exit criteria, suspension/resumption criteria

    E – Environment test environment needs

    D – Deliverables what is being delivered as part of the test


    I – Incidentals introduction, identification (of the document),

    approval authorities

    R – Risks risks and contingencies

    T – Tasks the test tasks that are involved in the testing


    Recommended Articles:  

  • Leave a Reply

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

    Scroll to Top