Test Management Software

Test Management Software

Instructions:

Identify any software that will be used to manage the testing. This includes the organization of the activities to be tested, and the management of defects. Date ranges between 1990 and 2010 can be used.

Example:

We will use "Test Manager" to manage the testing. Both the test team and applications development will have access and be able to update the status of defects.

 Testing Software

Instructions:

If any automated testing software such as WinRunner is to be used, detail the software. Also identify if the software will need to be purchased.

Performance Testing Software

Instructions:

If any performance testing software is to be used, detail the software. Also identify if the software will need to be purchased. In some cases, performance testing may be a separate activity to UAT.

Summary

The template above covers most of the normal issues that need to be in a strategy. For each project there will be specific issues that need to be included. The document will robably not be completed by just one person. It will require input from a range of people who will have different areas of expertise. For example, release procedures will probably be the responsibility of someone in a system administration role. The more people you talk to, the more problems you will avoid. Part of the reason for developing a strategy is to prompt people to think about the impact on their area. Developing a test strategy is a critical part of test planning.