Scribd Logo
Upload

Welcome to Scribd!

  • 657 views

    Test Plan Sample

    Uploaded by

    Jake Huss
    The document defines a test plan as a document that describes the testing scope, activities, and approach. It identifies test items, features to be tested, test tasks, resources, schedule, and criteria for determining if a test passes or fails. The template provided covers common sections of a test plan such as introduction, test items, approach, environment, schedule, roles and responsibilities. Test plans can be at the master, phase, or type level and should be concise, specific, and updated as needed.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd

    Test Plan Sample

    Uploaded by

    Jake Huss
    657 views4 pages
    The document defines a test plan as a document that describes the testing scope, activities, and approach. It identifies test items, features to be tested, test tasks, resources, schedule, and criteria for determining if a test passes or fails. The template provided covers common sections of a test plan such as introduction, test items, approach, environment, schedule, roles and responsibilities. Test plans can be at the master, phase, or type level and should be concise, specific, and updated as needed.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document defines a test plan as a document that describes the testing scope, activities, and approach. It identifies test items, features to be tested, test tasks, resources, schedule, and criteria for determining if a test passes or fails. The template provided covers common sections of a test plan such as introduction, test items, approach, environment, schedule, roles and responsibilities. Test plans can be at the master, phase, or type level and should be concise, specific, and updated as needed.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    657 views4 pages

    Test Plan Sample

    Uploaded by

    Jake Huss
    The document defines a test plan as a document that describes the testing scope, activities, and approach. It identifies test items, features to be tested, test tasks, resources, schedule, and criteria for determining if a test passes or fails. The template provided covers common sections of a test plan such as introduction, test items, approach, environment, schedule, roles and responsibilities. Test plans can be at the master, phase, or type level and should be concise, specific, and updated as needed.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 4
    At a glance
    Powered by AI
    The key takeaways from the document are that a test plan is a document that describes the scope, approach, resources and schedule of intended test activities. It identifies items to be tested, features, tasks, responsibilities and criteria for determining pass/fail. Different types of test plans discussed are master test plan, testing level specific plans and testing type specific plans.

    The different types of test plans mentioned are Master Test Plan, Testing Level Specific Test Plans (Unit Test Plan, Integration Test Plan, System Test Plan, Acceptance Test Plan) and Testing Type Specific Test Plans (Performance Test Plan, Security Test Plan).

    The sections that should be included in a test plan according to the given template are Test Plan Identifier, Introduction, References, Test Items, Features to be Tested, Features not to be Tested, Approach, Item Pass/Fail Criteria, Suspension Criteria and Resumption Requirements, Test Deliverables, Test Environment, Estimate, Schedule, Staffing and Training Needs, Responsibilities, Risks, Assumptions and Dependencies, Approvals.

    TEST PLAN DEFINITION A Software Test Plan is a document describing the testing scope and activities.

    It is the basis for formally testing any software/product in a project. ISTQB Definition

    test plan: A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice,and any risks requiring contingency planning. It is a record of the test planning process. master test plan: A test plan that typically addresses multiple test levels. phase test plan: A test plan that typically addresses one test phase.

    TEST PLAN TYPES

    One can have the following types of test plans:


    Master Test Plan: A single high-level test plan for a project/product that unifies all other test plans. Testing Level Specific Test Plans: Plans for each level of testing. o Unit Test Plan o Integration Test Plan o System Test Plan o Acceptance Test Plan Testing Type Specific Test Plans: Plans for major types of testing like Performance Test Plan and Security Test Plan.

    TEST PLAN TEMPLATE The format and content of a software test plan vary depending on the processes, standards, and test management tools being implemented. Nevertheless, the following format, which is based on IEEE standard for software test documentation, provides a summary of what a test plan can/should contain. Test Plan Identifier:

    Provide a unique identifier for the document. (Adhere to the Configuration Management System if you have one.)

    Introduction:

    Provide an overview of the test plan. Specify the goals/objectives. Specify any constraints.

    References:

    List the related documents, with links to them if available, including the following: o Project Plan o Configuration Management Plan

    Test Items:

    List the test items (software/products) and their versions.

    Features to be Tested:

    List the features of the software/product to be tested.

    Provide references to the Requirements and/or Design specifications of the features to be tested

    Features Not to Be Tested:


    List the features of the software/product which will not be tested. Specify the reasons these features wont be tested.

    Approach:

    Mention the overall approach to testing. Specify the testing levels [if it's a Master Test Plan], the testing types, and the testing methods [Manual/Automated; White Box/Black Box/Gray Box]

    Item Pass/Fail Criteria:

    Specify the criteria that will be used to determine whether each test item (software/product) has passed or failed testing.

    Suspension Criteria and Resumption Requirements:


    Specify criteria to be used to suspend the testing activity. Specify testing activities which must be redone when testing is resumed.

    Test Deliverables:

    List test deliverables, and links to them if available, including the following: o Test Plan (this document itself) o Test Cases o Test Scripts o Defect/Enhancement Logs o Test Reports

    Test Environment:

    Specify the properties of test environment: hardware, software, network etc. List any testing or related tools.

    Estimate:

    Provide a summary of test estimates (cost or effort) and/or provide a link to the detailed estimation.

    Schedule:

    Provide a summary of the schedule, specifying key test milestones, and/or provide a link to the detailed schedule.

    Staffing and Training Needs:


    Specify staffing needs by role and required skills. Identify training that is necessary to provide those skills, if not already acquired.

    Responsibilities:

    List the responsibilities of each team/role/individual.

    Risks:

    List the risks that have been identified. Specify the mitigation plan and the contingency plan for each risk.

    Assumptions and Dependencies:


    List the assumptions that have been made during the preparation of this plan. List the dependencies.

    Approvals:

    Specify the names and roles of all persons who must approve the plan. Provide space for signatures and dates. (If the document is to be printed.)

    TEST PLAN GUIDELINES

    Make the plan concise. Avoid redundancy and superfluousness. If you think you do not need a section that has been mentioned in the template above, go ahead and delete that section in your test plan. Be specific. For example, when you specify an operating system as a property of a test environment, mention the OS Edition/Version as well, not just the OS Name. Make use of lists and tables wherever possible. Avoid lengthy paragraphs. Have the test plan reviewed a number of times prior to baselining it or sending it for approval. The quality of your test plan speaks volumes about the quality of the testing you or your team is going to perform. Update the plan as and when necessary. An out-dated and unused document stinks and is worse than not having the document in the first place.

    You might also like