Project Test Plans

• Software Unit Test Plan and Report Guidelines
  Reduce overall development time and costs by finding and fixing errors before they get lost in the end-to-end tests. It is far simpler to detect and correct problems during unit testing -- that is, testing the smallest possible unit of an application -- than it is after integration. This template includes an overview of unit testing, step-by-step process guidelines, and sample documents for creating your own formal testing procedures, which can then be used for reliability testing by third parties as well as in-house resources.
• Integration Plan
  Avoid the "Big Bang" theory of integration! Don't throw it all in the mix and hope for the best. This plan will help you document how the hardware, software and other components will be integrated prior to system test.
• QA and Beta Test Manager Job Descriptions
  Testing management roles are not to be taken lightly and not for the faint of heart! Nor should these roles be relegated to the end of the project only, as they so often are. These job descriptions show the true breadth of these roles done right, and should make any project manager reconsider how to engage and deploy these team members effectively throughout the project.
• 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.
• 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 for getting customer and end user reaction to the functions and features. Includes sections for important detailed planning elements that are often overlooked and can drastically affect both the scope and the effectiveness of the tests.
• User Acceptance Test Plan
  Annotated outline for testing to be executed by users of a system or application prior to the production-level build and deployment. User Acceptance Testing (UAT) is the formal means for ensuring that a new system or application actually meets the essential user requirements. The plan includes sections such as scope of testing, test team, training needed, and a testing timeline to ensure that this critical activity is planned for and executed thoroughly.
• Master Test List
  Provides a tabular format for listing the tests to be run during a testing cycle (such as Beta, System test, etc.), with a place to categorize and describe each test, provide pass-fail criteria, indicate the planned run day or week; and log pass-fail test results. Usable on any project, but especially useful for smaller projects, where it can be THE test plan/test case document, while still providing a quick-reference tracking document for what has been tested, what has failed, what is left to test etc.

©Copyright 2000-2008 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