Test Plan

Test Objectives

Provides a description of  the purpose for testing and concise summary of test plan objectives.  Include products to be delivered, work activities with responsible roles, milestones, required resources, and schedule.

Example:

The purpose of testing CollegeNet’s–25Live event management system is to evaluate the feasibility and the performance of the scheduling management architecture. It is critical that all of the scheduling management interfaces be tested as well as the subsystem performance at this early stage.

The most critical performance measures to test are:

• response and access for on-campus login to the scheduling management system.
• response and access for off-campus login to the scheduling management system.
• response time to access classroom scheduling·response time to access event. management scheduling.
• response time to access event calendaring.
• primary-stakeholder response time when system receives event inquiry.
• primary-stakeholder response time when system batches classroom assignments.
• secondary-stakeholder access to view and/or approve event.

Test Approach

Describe the sources for requirements that will be used to drive the test design.  Work with the developers and integrators to ensure the test team/analyst is provided these sources or information in a timely manner.  This flow of information ensures that testing develops a good understanding of the requirements.

Example:

From the areas below select the appropriate testing for the project as required.

• Unit Testing:

The purpose of this testing is to ensure that the program logic is complete, correct and performs as designed.  Testing is conducted to verify the implementation of the design for one element or collection of elements, also known as Component Testing.      

• Integration Testing:

The purpose of this testing is to ensure that the design objectives are met and system complies with operational requirements. Testing is conducted on the software elements, hardware elements, or on a combination of both elements until the entire system is integrated, also known as System Testing.

• Performance Testing:

The purpose of this testing is to ensure that the application performs to the customer’s expectations; such as response time, availability, portability, and scalability.

• Recovery Testing:

The purpose of this testing is to ensure that the application restarts, backups, and recovery facilities operate as designed.

• Regression Testing:

The purpose of this testing is to ensure that applied application changes have no adverse effects on previously tested functionality.

• User Acceptance Testing:
  ​​​​
  The purpose of this testing is to determine whether or not the system satisfies the acceptance criteria; acceptance testing ensures that the customer’s objectives are met.

Test Case

The purpose of the test case is define a set of conditions under which a tester will determine whether an application, software system, or one of its features is working as it was originally designed or established to do.

Example:

Test Resources

Provide information about  team  members  responsible  for  testing  and  provide  their responsibility. Indicate who is responsible for signing off on testing once completed.

Example: