a) Management of Tests
b) Scheduling of Tests
c) Management  of Testing Activities
d) Interfaces to other testing tools
e) Traceability

 

Only a,b & c
Only b,c & d
Only d & e
All a,b,c,d & e

No
Yes
Only results of automated tests can be stored

Storing Requirements
Identifying undefined , missing or to be defined requirements
Traceability of Requirements
Generating Test Data

Scheduling of Tests
Storing Requirements
Traceability
Information About Versions and builds of Software and Test Ware

a) Sorting and Storing Review Comments
b)Communicating Comments to relevant people
c) Keeping track of  review comments , including defects
d) Traceability between review comments & review documents

 

All a,b,c, & d
Only a,b& c
Only a & b
Only b,c & d

Calculate Cyclomatic Complexity
Sorting and Storing Review Comments
Interfaces to other testing tools
Information About Versions and builds of Software and Test Ware

Identify Inconsistencies or defects in Models
Identifying undefined , missing or to be defined requirements
Help in prioritization of tests in accordance with the model in review
predicting system response under various levels of loads

generating test input values
generating expected results
Screen- Scrapper
Storing Requirements

Data Anonymization
Create new records populates with random data
Create large number of similar records from a template
Screen- Scrapper

Sorting and Storing Review Comments
Data Anonymization
executing tests from a stored scripts
Generating Test Data

code coverage measurement
support for debugging
recording pass / fail status
Load Testing

Comparing Test Cases Designed
Comparing Test Data
Comparing Test Steps
Comparing Test Results

Identifying Coverage Items
Reporting coverage items which are not covered yet
generating stubs and drivers
Generating Test Data

Identifying Viruses
Identify Denial of Service Attacks
Identifying Weakness in Passwords for files and passwords
Identifying Performance Bottlenecks

Static analysis tools and test execution tools.
Review process support tools, static analysis tools and coverage measurement tools.
Dynamic analysis tools and modeling tools.
Review process support tools, static analysis tools and modeling tools.

Greater quality of code, reduction in the number of testers needed, better objectives for testing
Greater repeatability of tests, reduction in repetitive work, objective assessment.
Greater responsiveness of users, reduction of tests run, objectives not necessary.
Greater quality of code, reduction in paperwork, fewer objections to the tests.

Unrealistic expectations, expecting the tool to do too much.
Insufficient reliance on the tool, i.e. still doing manual testing when a test execution tool has been purchased
The tool may find defects that aren't there.
The tool will repeat exactly the same thing it did the previous time.

Data-driven and keyword-driven
Capture-driven and keyhole-driven
Playback-driven and keyword-driven
Data-driven and capture-driven

Assess organizational maturity, strengths and weaknesses.
Roll out the tool to as many users as possible within the organization.
Evaluate the tool features against clear requirements and objective criteria.
Identify internal requirements for coaching and mentoring in the use of the tool.

Decide which tool to acquire.
Decide on the main objectives and requirements for this type of tool.
Evaluate the tool vendor including training, support and commercial aspects.
Decide on standard ways of using, managing, storing and maintaining the tool and the test assets