ISTQB 6

1. What are the potential benefits from using tools in general to support testing?

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

Data-driven and capture-driven

Capture-driven and keyhole-driven

Playback-driven and keyword-driven

Test management and control.

Test specification and design.

Test execution and logging.

Performance and monitoring.

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.

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.

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.