Software Testing

Foundation Level-CTFL.
Syllabus 2018

Tool support for testing

Presented by: Ahmed Adel -

CMMI Associate
Outlines

➔ Effective use of tools: potential benefits and risks

➔ Types of test tools
➔ Introducing a tool into an organization
❑ Tool
TypesSupport
of test tools
for Testing

Any tool used for the aid of testing, such as tools used in testing
as test execution tools, test data generation tools and result
comparison tools.

Tools support can Have the following objectives:

● Improve the efficiency of test activities by automating

repetitive tasks or supporting manual test activities.
● Automate activities that require significant resources to do
manually.
● Automate activities that can not be done manually.
● Increase reliability of testing.
❑ Effective Use Of Tools: Potential
Benefits And Risks.

Benefits of using tools:

• Repetitive work is reduced.

• Greater consistency and repeatability.
• Objective assessment.
• Ease of access to information about tests or testing.
 Risks of using tools:

• Unrealistic expectations for the tool and over-reliance on

the tool.
• Underestimating the time, cost and effort for the initial
introduction of a tool.
• Underestimating the time and effort needed to achieve the
desired goals.
INTRODUCING A TOOL INTO AN ORGANIZATION

The Main considerations for selecting a tool for an

organization include:
• Assessment of organizational maturity, strengths and weaknesses and identification of
opportunities for an improved test process supported by tools.
• Evaluation against clear requirements and objective criteria.
• A proof-of-concept, by using a test tool during the evaluation phase to establish whether
it performs effectively with the software under test and within the current infrastructure
or to identify changes needed to that infrastructure to effectively use the tool.
• Evaluation of the vendor (including training, support and commercial aspects) or service
support suppliers in case of non-commercial tools.
• Identification of internal requirements for coaching and mentoring in the use of the tool.
Introducing a Tools into an organization starts with a pilot
project that has the following objectives:

• Learn more detail about the tool.

• Evaluate how the tool fits with existing processes and practices,
and determine what would need to change.
• Decide on standard ways of using, managing, storing and
maintaining the tool and the test assets (e.g., deciding on naming
conventions for files and tests, creating libraries and defining the
modularity of test suites).
• Assess whether the benefits will be achieved at reasonable cost.
The Success Factors for the deployment of the
tool:

• Rolling out the tool to the rest of the organization incrementally.

• Adapting and improving processes to fit with the use of the tool.
• Providing training and coaching/mentoring for new users.
• Defining usage guidelines.
• Implementing a way to gather usage information from the actual
use.
• Monitoring tool use and benefits.
Test tool classification
Tool support for management of testing and
tests.

• Test Management tools.

• Requirements management tools.
• Incident management tools.
• Configuration management tools.

Tool support for Static testing.

• Review Tools
• Static Analysis Tools
 Tool support for Test specification.
• Test Design tools (used to generate test inputs or Tests from
Requirements).
• Test data preparation tools ( Manipulate test data to be used
during the execution of tests).

Tool support for Test execution and logging.

• Test Execution Tools.
• Test Harness / Unit Test Framework Tools (D) .
• Coverage Measurement Tools (D).
• Security Testing Tools.