Skip to main content

Software Test Planning

  • Chapter
  • First Online:
  • 2842 Accesses

Part of the book series: Undergraduate Topics in Computer Science ((UTICS))

Abstract

Testing is a sub-project of a project and needs to be managed as such, and so good planning and monitoring and control are required. Test planning involves defining the scope of the testing to be performed; defining the test environment; estimating the effort required to define the test cases and to perform the testing; identifying the resources needed (including people, hardware, software, and tools); assigning the resources to the tasks; defining the schedule; and identifying any risks to the testing and managing them.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Notes

  1. 1.

    These are the risk management activities in the PRINCE2 methodology.

  2. 2.

    The consequences of underestimating a project include the project being delivered late, with the project team working late nights and weekends to recover the schedule, quality being compromised with steps in the process omitted, and so on.

  3. 3.

    Unless “Go ask Fred” is the name of the estimation methodology or the estimation tool employed.

  4. 4.

    This quotation is adapted from Benjamin Franklin (an inventor and signatory to the American declaration of independence).

  5. 5.

    The project board in the PRINCE2 methodology includes roles such as the project executive, senior supplier, senior user, project assurance, and the project manager. These roles have distinct responsibilities.

  6. 6.

    The project plan will usually specify a tolerance level for schedule and spending, where the project may spend (perhaps less than 10%) in excess of the allocated capital for the project before seeking authorization for further capital funding for the project.

  7. 7.

    Often, a colour coding mechanism is employed with a red flag indicating a serious issue; amber highlighting a potentially serious issue; and green indicating that everything is ok.

Reference

  • Office of Government Commerce (2004) Managing successful projects with PRINCE 2. The Stationary Office, London

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2019 Springer Nature Switzerland AG

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

O’Regan, G. (2019). Software Test Planning. In: Concise Guide to Software Testing. Undergraduate Topics in Computer Science. Springer, Cham. https://doi.org/10.1007/978-3-030-28494-7_5

Download citation

  • DOI: https://doi.org/10.1007/978-3-030-28494-7_5

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-030-28493-0

  • Online ISBN: 978-3-030-28494-7

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics