Tool support for testing

TOOL SUPPORT FOR TESTING
Oleh
Amelia Septia Roza
11453204909
Program Studi Sistem Informasi
Fakultas Sains dan teknologi
Universitas Islam Negeri Sultan Syarif Kasim Riau

1. Types of Test Tool
The list of the various tool types in terms of their general functionality :
a. Test tool classification
b. Tool support for management of testing and tests
c. Tool support for static testing
d. Tool support for test specification
e. Tool support for test execution and logging
f. Tool support for performance and monitoring
g. Tool support for specific application areas (Kl)
h. Tool support using other tools

a. Test Tool Classification
The tools are grouped by the testing activities or areas that are supported by a set of
tools, for example, tools that support management activities, tools to support static testing,
etc.
b. Tool support for management of testing and tests
What does 'test management' mean? It could be 'the management of tests' or it could
be 'managing the testing process'. The tools in this broad category provide support for
either or both of these. The management of testing applies over the whole of the software
development life cycle, so a test management tool could be among the first to be used in a
project.

c. Tool support for static testing
 Review process support tools
 Static analysis tools (D)
 Modeling tools (D)
d. Tool support for test specification
 Test design tools
 Test data preparation tools

e.Tool support for test execution and logging
 Test execution tools
 Test harness/unit test framework tools (D)
 Test comparators
 Coverage measurement tools (D)
 Security tools
f. Tool support for performance and monitoring
The tools described in this section support testing that can be carried out on a system
when it is operational, i.e. while it is running. This can be during testing or could be after a
system is released into live operation.
 Dynamic analysis tools (D)
 Monitoring tools

g. Tool support for specific application areas (Kl)
There are also further specializations of tools within these clas- sifications. For
example there are web-based performance-testing tools as well as performance-
testing tools for back-office systems. There are static analysis tools for specific
development platforms and programming languages, since each programming
language and every platform has distinct characteristics. There are dynamic analysis
tools that focus on security issues, as well as dynamic analysis tools for embedded
systems.
h. Tool support using other tools
The tools described in this chapter are not the only tools that a tester can make
use of. You may not normally think of a word processor or a spreadsheet as a testing
tool, but they are often used to store test designs, test scripts or test data.

2. Effective Use of Tools : Potential Benefits and
Risks
The reason for acquiring tools to support testing is to gain
benefits, by using a software program to do certain tasks that
are better done by a computer than by a person.
a. Potential benefits of using tools
b. Risks of using tools
c. Special considerations for some types of tools

Risks
a. Potential benefits of using tools
There are many benefits that can be gained by using tools to support testing,
whatever the specific type of tool. Benefits include:
 reduction of repetitive work;
 greater consistency and repeatability;
 objective assessment;
 ease of access to information about tests or testing.

Risks
b. Risks of using tools
There are many risks that are present when tool support for testing is
introduced and used, whatever the specific type of tool. Risks include:
 unrealistic expectations for the tool;
 underestimating the time, cost and effort for the initial introduction of a tool;
 underestimating the time and effort needed to achieve significant and con
tinuing benefits from the tool;
 underestimating the effort required to maintain the test assets generated by
the tool;
 over-reliance on the tool.

Risks
c. Special considerations for some types of tools
 Test execution tools
 Performance testing tools
 Static analysis tools
 Test management tools

3. Introducing A Tool Into An Organization
 Main principles
 Pilot project
 Success factors

 Main principles
The place to start when introducing a tool into an organization is not with the tool - it
is with the organization. In order for a tool to provide benefit, it must match a need within
the organization, and solve that need in a way that is both effective and efficient.
The following factors are important in selecting a tool:
 assessment of the organization's maturity (e.g. readiness for change);
 identification of the areas within the organization where tool support will help to
improve testing processes;
 evaluation of tools against clear requirements and objective criteria;
 proof-of-concept to see whether the product works as desired and meets the
requirements and objectives defined for it;
 evaluation of the vendor (training, support and other commercial aspects) or open-
source network of support;
 identifying and planning internal implementation (including coaching and mentoring
for those new to the use of the tool).

 Pilot project
The objectives for a pilot project for a new tool are:
 to learn more about the tool (more detail, more depth);
 to see how the tool would fit with existing processes or documentation, how those
would need to change to work well with the tool and how to use the tool to
streamline existing processes;
 to decide on standard ways of using the tool that will work for all potential users
(e.g. naming conventions, creation of libraries, defining modularity, where different
elements will be stored, how they and the tool itself will be maintained);
 to evaluate the pilot project against its objectives (have the benefits been achieved
at reasonable cost?).

 Success factors
Success is not guaranteed or automatic when implementing a testing tool, but many
organizations have succeeded. Here are some of the factors that have contributed to success:
 incremental roll-out (after the pilot) to the rest of the organization;
 adapting and improving processes, testware and tool artefacts to get the best fit and balance
between them and the use of the tool;
 providing adequate training, coaching and mentoring of new users;
 defining and communicating guidelines for the use of the tool, based on what was learned in the
pilot;
 implementing a continuous improvement mechanism as tool use spreads through more of the
organization;
 monitoring the use of the tool and the benefits achieved and adapting the use of the tool to take
account of what is learned.

Reference
 Graham,d., et al.2006. Foundation of Software Testing:
ISTQB certification London, UK : International Thomson
Business Press

Thank You
 https://uin-suska.ac.id/
 https://fst.uin-suska.ac.id/
 https://sif.uin-suska.ac.id/

Tool support for testing

More Related Content

What's hot (20)

Similar to Tool support for testing (20)

Recently uploaded (20)

Tool support for testing