0% found this document useful (0 votes)
72 views4 pages

CH6 - Tool Support For Testing: Quick Notes

This document discusses tool support for testing. It covers the types of tools used in test management, static testing, test specification, test execution and logging, and performance/monitoring. Potential benefits of tools include reduced repetitive work, consistency and repeatability. Risks include unrealistic expectations and overreliance. When introducing a new tool, organizations should assess maturity, identify areas of need, evaluate tools, conduct a proof of concept, and plan training. A pilot can help learn about the tool and fit with processes before full deployment.

Uploaded by

Blabla
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
72 views4 pages

CH6 - Tool Support For Testing: Quick Notes

This document discusses tool support for testing. It covers the types of tools used in test management, static testing, test specification, test execution and logging, and performance/monitoring. Potential benefits of tools include reduced repetitive work, consistency and repeatability. Risks include unrealistic expectations and overreliance. When introducing a new tool, organizations should assess maturity, identify areas of need, evaluate tools, conduct a proof of concept, and plan training. A pilot can help learn about the tool and fit with processes before full deployment.

Uploaded by

Blabla
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Quick Notes

CH6 – Tool Support for Testing

Number of Questions – 4 (K1-3, K2-1, K3-0) Duration – 45 minutes

1] Probe Effect

The effect on the component or system when it is being measured. E.g.


Performance may be slightly worse when performance testing tools are used. The
delays introduced by insertion/removal of code instrumentation may result in a
non-functioning application, or unpredictable behaviour. By attaching a multi-
meter, oscilloscope, or other testing device via a test probe, small amounts of
capacitance, resistance, or inductance may be introduced in sensitive circuitry
these can lead to unexpected failures, or conversely, unexpected fixes to failures.

2] Types of test tool

a) Tool support for management of testing and tests

Test Management Tools - Management of tests, Scheduling of tests to be


executed, Management of testing activities, Interfaces to other tools, Traceability
of tests, Logging test result, Preparing progress report

Requirement Management Tools - Store requirements, check for consistency,


allow requirements to be prioritized, trace changes, coverage of requirements etc.

Incident Management Tools - Store and manage incident reports, facilitating


prioritization, assessment of actions to people and attribution of status etc.

Configuration management tools - Storing information about versions and builds


of software and test ware, traceability between software and testware and
different, versions, Keeping track of which version belongs with which
configuration build and release management, Base lining, Access control
Quick Notes 6: Tool Support for Testing
Created by: Sagar Joshi 1
https://www.udemy.com/istqb-foundation-level-certification-ctfl-training/
b) Tool support for static testing

Review Process Support Tools - Store information, store and communicate review
comments etc.

Static Analysis Tools - The enforcement of coding standards, the analysis of


structures and dependencies, aiding in understanding the code etc.

Modelling Tools - Validate models of the software; find defects in data model,
state model or an object model etc.

c) Tool support for test specification

Test Design Tools - Generate test inputs or executable tests, generate expected
out comes etc.

Test Data Preparation Tools - Preparing test data, Manipulate databases, files or
data transmissions to set up test data etc.

d) Tool support for test execution and logging

Test Execution Tools - Record tests, automated test execution, use inputs and
expected outcomes, compare results with expected outcomes, repeat tests,
dynamic comparison, manipulate the tests using scripting language etc.

Test Harness/Unit Test Framework Tools - Test components or part of a system


by simulating the environment; provide an execution framework in middle ware
etc.

Test Comparators - Determine differences between files, databases or test results


post-execution comparison, may use test oracle if it is automated etc.

Coverage Measurement Tools - Measure the percentage of specific types of code


structure (ex: statements, branches or decisions, and module or function calls)

Security Tools - Check for computer viruses and denial of service attacks, search
for specific vulnerabilities of the system etc.

Quick Notes 6: Tool Support for Testing


Created by: Sagar Joshi 2
https://www.udemy.com/istqb-foundation-level-certification-ctfl-training/
e) Tool support for performance and monitoring

Dynamic Analysis Tools - Detect memory leaks, identify time dependencies and
identify pointer arithmetic errors.

Performance Testing Tools - Measure load or stress, Monitor and report on how a
system behaves a variety of simulated usage conditions, simulate a load on an
application/a database/or a system environment, repetitive execution of tests etc.

Monitoring Tools - Continuously analyse, verify and report on specific system


resources; store information about the version and build of the software and
testware, and enable traceability.

3] Potential benefits and risks of tool support for testing

Benefits:

 Repetitive work is reduced


 Greater consistency and repeatability
 Objective assessment
 Ease of access to information about tests or testing

Risks:

 Unrealistic expectations for the tool


 Underestimating the time and effort needed to achieve significant and
continues benefits from the tool
 Underestimating the effort required to maintain the test assets generated
by the tool
 Over-reliance on the tool

Quick Notes 6: Tool Support for Testing


Created by: Sagar Joshi 3
https://www.udemy.com/istqb-foundation-level-certification-ctfl-training/
4] Introducing a tool into an organization

The following factors are important in selecting a tool:

 Assessment of the organization maturity


 Identification of the areas within the organization where tool support will
help to improve testing process
 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 to Identifying and planning internal
implementation (including coaching and mentoring for those new to the use
of the tool)

The objectives for a pilot project for a new tool

 To learn more about the tool


 To see how the tool would fit with existing processes or documentation
 To decide on standard ways of using the tool that will work for all potential
users
 To evaluate the pilot project agonist its objectives

Successes factors for the deployment of the new tool within an organization

 Rolling out the tool to the rest of the organization incrementally


 Adapting and improving process to fit with the use of the tool
 Providing training and coaching/mentoring for new users.
 Defining usage guidelines
 Implementing a way to learn lessons from tool use.
 Monitoring tool use and benefits.

Quick Notes 6: Tool Support for Testing


Created by: Sagar Joshi 4
https://www.udemy.com/istqb-foundation-level-certification-ctfl-training/

You might also like