Resource Index > Technical Work > Testing

Testing

Testing is a cornerstone activity of a product development process. It's one of the activities used to verify that a design generates the correct outputs for a defined set of inputs and validate a design as meeting its requirements and providing adequate fitness for use. Testing is important in all product and system development projects, but in software development groups that lack of a strong development process or methodology, testing can become the primary way of finding and removing design and implementation defects. Testing activities should never replace good quality planning, but teams should still be sure they're adequately testing and reporting results during the project. These resources will help.

How can we help you with your testing plans and activities?

Examples of Testing Plans and Bug Tracking
These resources provide real-world examples of project test plans and test result tracking.

For Members
These resources are free to registered members. Register or login for access.
  • Integration Plan
    An outline for documenting how the hardware and/or software in a system will be integrated before system test. Great for making sure the integration steps have been thought through (rather than defining an amorphous block of time for integration then hoping everything comes out at the end!)
  • Software Bug Fix WBS
    WBS for an efficient but reasoned bug-fix project, which can be expanded for a minor enhancement or re-engineering effort or used as a checklist for small clean up projects. The included Word file provides an overview and explanation of the MS Project WBS.
For Subscribers
These resources are for Premium subscribers. Subscribe to get access, or find out more about our free trial for new subscribers.
  • Software Test Transfer Forms
    Practical forms to accompany a software build when Development sends it Testing, to serve as a record of what is being transferred, testing instructions, and ultimately a record of what was tested and the results.
  • User Acceptance Test Plan (IT)
    Annotated outline for testing to be executed by users of a system or application prior to the production-level build and deployment.
  • Master Test List
    A tabular format for listing the tests to be run during a testing cycle, such as Beta test, System test, etc.
  • System Test Plan
    Annotated document outline for a System Test Plan describing how the team will internally verify that the system as a whole functions as planned under a variety of use conditions, before performing any external customer beta or acceptance testing. Also includes System Test Report outline for documenting and communicating results.
  • Software Quality Release Criteria
    A short document that captures the criteria with which the software's quality will be judged at various stages of the project.
Guidelines and Suggestions for Test Planning and Tracking
These resources help explain what constitutes a good test plan, when you should do test planning, and proven ways to track bugs and issues that testing uncovers.

For Guests
These resources are available to everyone, no login required.
For Members
These resources are free to registered members. Register or login for access.
  • Software Unit Testing
    Unit testing is cost-effective, reliable, and often reveals insidious bugs that may not turn up when a system is tested against requirements. This paper provides an overview of practical, ground-level concerns when developing unit testing procedures.
  • Software Unit Test Plan and Report Guidelines
    An overview of unit testing, step-by-step process guidelines, and sample documents for creating your own formal testing procedures.
  • Tools and Equipment List
    This template provides a format for thinking through and documenting the tools (e.g. hardware, software) and equipment needed during a project for testing, prototyping, etc.
  • Release Decision Process Guidelines
    Process that can be used near the end of a project to systematically review open issues and determine which ones must be corrected before release.
For Subscribers
These resources are for Premium subscribers. Subscribe to get access, or find out more about our free trial for new subscribers.
  • Project Test Plan
    This plan outline walks you through the process from initial test planning to documentation and project implementation, with detailed annotations and suggestions for test types you may want to consider.
  • Beta Test Plan
    An annotated outline for a full beta test plan document -- testing that is often critical for exercising the product, service, or system in a way that cannot be duplicated in the lab -- and getting customer and end user reaction to the functions and features.
  • Project Overview Test Plan
    This plan hows how to document at a high level how a system will be tested in different ways during the project to ensure it meets its user requirements and technical specifications and functions properly.
  • QA and Beta Test Manager Job Descriptions
    Job descriptions for QA Manager and Beta Test Program Manager which show the true breadth of these roles when done right.
  • Software Release Life Cycle Phase 7: System Test
    Defines documents, reports and activities needed while executing a series of tests with the primary purpose of fully exercising the software release being created.
  • Software Release Life Cycle Phase 8: Internal Testing (Alpha)
    Defines testing and review activities to run a software release through its final paces internally before being exposed to an external customer.
  • Software Release Life Cycle Phase 9: External Testing (Beta)
    Defines testing and review activities to exercise a software release in a "real world" environment at one or more customers.
Other Options
  • Review our book list for several helpful books on testing and related subjects.
  • Project Test Plans Bundle
    This bundle provides practical tools for planning and executing thorough tests of your project's deliverables -- before they are deployed to the customer!
Typical Testing Issues and Answers to Common Questions
How do I ensure that I'm doing adequate testing without going overboard? How can I measure the overall effectiveness of my testing in order to justify what I spend on it to my management? How can I use these measures to improve my testing process? These resources will help.

For Guests
These resources are available to everyone, no login required.
For Members
These resources are free to registered members. Register or login for access.
  • Release Decision Process Guidelines
    Process that can be used near the end of a project to systematically review open issues and determine which ones must be corrected before release.
For Subscribers
These resources are for Premium subscribers. Subscribe to get access, or find out more about our free trial for new subscribers.



©Copyright 2000-2017 Emprend, Inc. All Rights Reserved.
About us   Site Map   View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy

Get Our Newsletter
Get our latest content delivered to your inbox, every other week. New case studies, articles, templates, online courses, and more. Check out our Newsletter Archive for past issues.

Follow Us!
Linked In Facebook Twitter RSS Feeds

Got a Question?
Drop us an email or call us toll free:
888-722-5235
Learn more about ProjectConnections, our contributors, and our membership levels and product options.