How to Write a Test Plan

How to Write a Test Plan

by

Download the article

wikiHow is a “wiki,” similar to Wikipedia, which means that many of our articles are written by multiple authors. To create this article, 21 people, some anonymous, worked to edit and improve it over time. There are 8 references cited in this article, which can be found at the bottom of the page. wikiHow marks an article as reader-approved after it receives enough positive comments. In this case, 80% of the readers who voted found the article useful, earning us Reader Approved status. This article has been viewed 352,168 times. Know more…

Test plans describe the process of testing the functionality of the software. A test plan describes in detail each step taken to achieve a specific result and states the objective of each action. The plan also outlines the anticipated resources, risks, and personnel involved in the test. You should use a test plan if you want to eliminate bugs and other bugs in your software before it is made available to users. Follow the steps below to create a test plan.

  1. Image titled Write a test plan Step 1

    Learn the basics. What you include in your test plan largely depends on the complexity of the software you plan to test. However, there are three basic sections that should always be included in a test plan: test coverage, test methods, and test responsibilities.

    • Test coverage defines what you will and will not test.
    • The test methods define how you will test each part defined in the “coverage” section.
    • The exam responsibilities assign tasks and responsibilities to different parties. This section should also include the information that each party will record and how it will be stored and reported.

  2. Image titled Write a test plan Step 2

    Familiarize yourself with the necessary IEEE standards documents. The Institute of Electrical and Electronics Engineers (IEEE) publishes international standards for testing and documenting software and systems development.[1]
    To keep your test plan at the highest level, check out the IEEE publications below:

    • 29119-1-2013, Software and Systems Engineering – Software Testing – Part 1: Concepts and definitions.[2]
    • 29119-2-2013, Software and systems engineering – Software testing – Part 2: Test processes.[3]
    • 29119-3-2013, Software and systems engineering – Software testing – Part 3: Test documentation.[4]
    • 829-2008, IEEE Standard for System and Software Test Documentation.[5]
    • 1008-1987 – IEEE Standard for Software Unit Testing.[6]

  3. Image titled Write a test plan Step 3

    Check the template. You can find test plan templates online. The best source for templates is the IEEE library, but access is paid.

    • Dublin City University also offers a free trial plan template, based on IEEE 829 standards.

  1. Image titled Write a test plan Step 4

    Write an introduction. Your introduction functions as an “executive summary” of the test plan: its goals, scope, and timeline. This should be short, as you will go into more detail in the following sections of the test plan.[7]

    • Your mission and scope statements should define, in general terms, the methods to be used in the testing process and the expected results. The scope statement should also include the most critical performance measures, as well as a list of what the test plan will not cover and why.
    • The schedule lists the time steps in which each phase of the test will be completed.
    • Related documents include any peripheral materials relevant to the current project, such as specification lists.

  2. Image titled Write a test plan Step 5

    Define your goals. Your test plan should clearly define what you will test and why you will test it. They should always be based on industry standards.[8]

    • Determine the scope of the test. What scenarios will be tested?
    • Determine what is beyond the scope of the test. What scenarios will not be tested?
    • Common scenarios include module testing, integration testing, system/acceptance testing, and beta testing.

  3. Image titled Write a test plan Step 6

    Write a section on the resources needed. This section describes all the resources required to complete the tests, including hardware, software, test tools, and personnel.[9]

    • When accounting for your staff, be sure to detail the responsibilities required of each member and the training required to carry out those responsibilities.
    • Be sure to document exact hardware and software specifications.

  4. Image titled Write a test plan Step 7

    Write a section on risks and dependencies. Describe in detail all the factors on which your project depends and the risks involved in each step. The acceptable level of risk in your project will help determine what you will and will not test.[10]

    • Consider the probability of various risks. You will need to prioritize critical areas.
    • Be aware of any vague or unclear requirements. Users often lack the experience to understand technical language or procedures, so user misunderstandings can be a risk.
    • Use your history of past “mistakes” to help identify areas of concern and further testing.

  5. Image titled Write a test plan Step 8

    Write a section about what you will test. Specify which new aspects to test and which old aspects to retest. Be sure to state the purpose of each test.

    • You can use software application inventories, IEEE guidelines, and other sources to help you determine this list.
    • This section also introduces your “deliverables”, that is, the data that you will deliver to the client after the test is complete.

  6. Image titled Write a test plan Step 9

    Write a section about what you will not test. List the features that will not be tested during the current project. Reasons not to test features include:

    • This feature will not be included in this version of the software.
    • The feature is low risk or has been used before without issues

  7. Image titled Write a test plan Step 10

    State your strategy. This section describes the general test strategy for your test plan. It will outline the rules and processes that will apply to the above tests.[11]

    • Include information about the tools that will be used, what metrics will be collected and at what level, how many configurations will be tested, and if there are any special testing requirements or procedures.

  8. Image titled Write a test plan Step 11

    Develop pass/fail criteria. These criteria will guide your test staff in knowing whether the test objectives have been achieved. This section can also include “exit criteria,” so your staff know when it’s acceptable to stop testing a particular feature.

    • It must also include a list of criteria for suspension and conditions for continuation. This information tells testers when to pause testing and what is an acceptable level of failure to resume testing.

  9. Image titled Write a test plan Step 12

    Write a list of documents that will be created during the test. Also known as “deliverables,” these documents are the data, reports, scripts, and results that the test will produce.

    • It’s a good idea to assign these results to the “owners” who are responsible for delivering them. Determine the terms in which they expire.

  10. Image titled Write a test plan Step 13

    Write the results section of your project. Make a list of the goals you hope to achieve during the testing process. Specify in detail who is responsible for final approvals.

See also  How to See Unsent Messages on Messenger?

Categories: How to
Source: newstars.edu.vn

1/5 - (1 vote)

Leave a Comment