Information Technology Reference
In-Depth Information
modifi cations for whatever new functionality that Version 2 provides. Functionality
in Version 1 no longer supported in Version 2 will require test script retirement.
11.7 THE LIABILITIES THAT TESTING TOOLS
CAN IMPOSE
Before the test manager can calculate a prospective test tool's return on investment,
he or she needs to be aware of all the costs that should be included in the calculation
denominator. Some of the costs are obvious. Some of the costs are hidden.
11.7.1 Testing Tool Costs—a Financial, Resources,
and Skills Issue
The most obvious cost of a testing tool is its price tag. This price tag can range from
several thousand dollars to almost a million dollars. Many tools have a base price
and some form of usage price. The usage price can be expressed in terms of licenses
by (1) the number of computers that will run the test tool, (2) the number of testers
who will use the tool, or (3) the peak number of sessions to be run at any given time.
To determine the total price tag of the test tool for your project, you will need fairly
detailed test plans that can be used to predict the number of licenses to buy. Buy too
few licenses and you impact your testing schedule. Buy too many licenses and you
have spent too much money on tools.
A less obvious cost of test tools is the computer equipment that they may require.
Many of the functional test tools run on the same hardware as the application. Addi-
tional equipment purchases for these tools are not automatically required. The com-
bination of computing resources for both the application and the test tool may cause
the test team to need larger capacity computers after all. All of the performance test
tools require additional hardware at least for the tool server. Because performance
tool server resources are not infi nite, the workloads you plan to test may require two
or more performance tool servers and ancillary network equipment.
A scheduling cost often overlooked is the test tool installation in the testing
environment. Normally, the testing environment is being set up while the testers are
deep into planning. The decision to use a testing tool will add tool installation time
to the testing environment setup schedule. The result is that when the testers expect
the testing environment to be available for test execution, the testing environment
may still be busy with test tool installation.
A resource cost often overlooked is the skill set for the chosen testing tool. The
testing environment setup activities will require a tool expert to install the chosen
tool and verify its correct operation. Later in the testing execution activities, the
same kind of tool expert will have to be consulted to determine whether the source
of a possible defect is really incorrect tool usage by testers. Once the testing tool is
available in the testing environment, there is a skill set issue for the test team. The
testers who will use the testing tool must have either prior experience with that tool
or be sent to training specifi c for that tool.
Search WWH ::




Custom Search