week 12
week 12
Implementation
Chapter 6: Tools Support for Testing
Lecture 38
Tool Support for Testing
Probe Effect
“The effect on the component or system when it is being
measured e.g. performance may be slightly worse when
performance or monitoring testing tools are being used.”
Test Tool Classification
Configuration
Test Management Tool Management Tool
Incident
Requirements Management Tool
Management Tool
1
Tool Support for Management of Testing
Test Management
The planning, estimating, monitoring and control of test activities, typically
carried out be the test manager.
1
Tool Support for Management of Testing
Characteristics of Test Management Tools
Management of tests
1.Keeping track of the data associated for a given set of tests.
2.Knowing which test need to run.
3.Number of test planned
4.Number of test written, run, passed, failed.
Scheduling of tests to be executed
1.Manually or by test execution tools
Management of testing activities
1.Time spent in test design, test execution
2.Whether we are on schedule or on budget
Traceability of tests, test results and defects to requirements
Preparing progress report
1.Tests run and passed
2.Defects fixed or outstanding
1
Tool Support for Management of Testing
Configuration
Test Management Tool Management Tool
Incident
Requirements Management Tool
Management Tool
1
Tool Support for Management of Testing
Test Management
The planning, estimating, monitoring and control of test activities, typically
carried out be the test manager.
1
Tool Support for Management of Testing
Characteristics of Test Management Tools
Management of tests
1.Keeping track of the data associated for a given set of tests.
2.Knowing which test need to run.
3.Number of test planned
4.Number of test written, run, passed, failed.
Scheduling of tests to be executed
1.Manually or by test execution tools
Management of testing activities
1.Time spent in test design, test execution
2.Whether we are on schedule or on budget
Traceability of tests, test results and defects to requirements
Preparing progress report
1.Tests run and passed
2.Defects fixed or outstanding
1
Tool Support for Management of Testing
Characteristics
1.Storing requirement statements
2.Storing information about requirement attributes
3.Checking consistency of requirements
4.Identifying undefined, missing or to be defined later
requirements.
5.Prioritizing requirements
6.Traceability requirements
1
Tool Support for Management of Testing
Characteristics
1.Storing information about the attributes of defects
2.Prioritizing defects
3.Assigning actions to people e.g. fix, confirmation test
4.Status e.g. open close, reject, fix, duplicate
5.Reporting of statistics e.g. average time open, total number of defects raised
open or closed.
1
Tool Support for Management of Testing
Characteristics
1.Storing information about the versions
2.Traceability between software and different versions
3.Keeping track of which version belongs to which configuration (OS, libraries,
browsers.)
1
Tool Support for Management of Testing
1
Tool Support for Static Testing
2.Formal review is one, when many people are involved or when the people
involved are in different geographical location, then tool support becomes
more beneficial.
3.It is possible to keep track of all the information for a review process using
spreadsheet and text document, but a review tool will more likely to do a better
job.
4.A review process support tool could automatically calculate the checking
rate.
2
Tool Support for Static Testing
Characteristics
1. Storing review comments
2. Sorting review comments
3. Communicating comments to relevant people
4. Keeping track of comments e.g. defects found and providing
statistical information about those defects.
5. Monitoring the review status e.g. passed, passed with
corrections, required review again.
2
Tool Support for Static Testing
Static Analysis
Analysis of software artifacts e.g. requirements or code carried out
without execution of those software artifacts.
2
Tool Support for Test Specification
2.Most test generation tools do not include an oracle i.e. they generate the test
input but do not generate the expected results.
4.Range of valid values can be used to identify boundary values and EP.
5.If the valid range is stored the tool can distinguish between values that should be
accepted and those that should generate an error message.
2
Tool Support for Test Specification
6.If the expected result of the input of a valid value is known, then that
expected result can also be included in the test case generated by test
design tool.
7.Test design tool may have only a partial oracle i.e. it may know which
input value are to be accepted and rejected.
8.Another type of test design tool is called screen scraper. It identifies all of
the buttons and input fields i.e. every button will be clicked and every list
box will be selected.
9.Another type of test tool may be handled with coverage tool. This tool
can calculate an input value that will cause execution to take a particular
path in order to increase coverage.
2
Tool Support for Test Specification
1- Requirements
2- Code
3- Test condition etc.
2
Tool Support for Test Specification