ISTQB 2011 11

True

False

Same as black box testing

Same as white box testing

Same as functional testing

None of the above.

Functional characteristics

Non functional characteristics

Both A. & B.

None of the above

Test Management tool

Requirements management tool

Configuration management tool

Static analysis too;

Test Plan and Test Cases

Test log and Test Status

Defect Tracking

All of the above

The probability the negative event will occur

The potential loss or impact associated with the event

Both A. and B.

Neither A. nor B.

Type of dynamic testing

Type of static testing

Neither dynamic nor static

Performed by the testing team

Informal Review

Walkthrough

Technical review

Inspection

Statement testing

Path testing

Data flow testing

State transition testing

Features to be tested

Incident reports

Risks

Schedule

Regression testing

Integration testing

System testing

User acceptance testing

Same as Alpha Testing

Same as Beta Testing

Combination of Alpha and Beta Testing

None of the above

Boundary value analysis

Usability testing

Performance testing

Security testing

Reviews cannot be performed on user requirements specifications.

Reviews are the least effective way of testing code.

Reviews are unlikely to find faults in test plans.

Reviews should be performed on specifications, code, and test plans.

The analysis of batch programs.

The reviewing of test plans.

The analysis of program code.

The use of black box testing.

It allows the identification of changes in user requirements.

It facilitates timely set up of the test environment.

It reduces defect multiplication.

It allows testers to become involved early in the project.

Post-release testing by end user representatives at the developer’s site.

The first testing that is performed.

Pre-release testing by end user representatives at the developer’s site.

Pre-release testing by end user representatives at their sites.

Supplements formal test design techniques.

Can only be used in component, integration and system testing.

Is only performed in user acceptance testing.

Is not repeatable and should not be used.

£4800; £14000; £28000

£5200; £5500; £28000

£28001; £32000; £35000

£5800; £28000; £32000

Find as many faults as possible.

Test high risk areas.

Obtain good test coverage.

Test whatever is easiest to test.

Is that there is some existing system against which test output may be checked.

Is that the tester can routinely identify the correct outcome of a test.

Is that the tester knows everything about the software under test.

Is that the tester knows everything about the software under test.

Inspection

Walkthrough

Testing

All of the above

Syntax testing

Equivalence partitioning

Stress testing

Modified condition/decision coverage

Incident resolution is the responsibility of the author of the software under test.

Incidents may be raised against user requirements.

Incidents require investigation and/or correction.

Incidents are raised when expected and actual results differ.

Road map for testing

Tells about the actual results and expected results

Both a and b

None of the above

In a system two different failures may have different severities.

A system is necessarily more reliable after debugging for the removal of a fault.

A fault need not affect the reliability of a system.

Undetected errors may lead to faults and eventually to incorrect behavior.

System tests are often performed by independent teams.

Functional testing is used more than structural testing.

Faults found during system tests can be very expensive to fix.

End-users should be involved in system tests.

Decision testing

Error guessing

Statement testing

Exploratory testing

A minimal test set that achieves 100% LCSAJ coverage will also achieve 100% branch coverage.

A minimal test set that achieves 100% path coverage will also achieve 100% statement coverage.

A minimal test set that achieves 100% path coverage will generally detect more faults than one that achieves 100% statement coverage.

A minimal test set that achieves 100% statement coverage will generally detect more faults than one that achieves 100% branch coverage.

1 and 2

1, 2 and 3

1, 2, 3 and 4

2 and 4

Moderator

Author

Reviewer

Recorder

Test Design tool

Test data preparation tool

Test execution tool

Test harness

None of the above

Possible communications bottlenecks in a program.

The rate of change of data values as a program executes.

The use of data on paths through the code.

The intrinsic complexity of the code.

Incidents should always be fixed.

An incident occurs when expected and actual results differ.

Incidents can be analysed to assist in test process improvement.

An incident can be raised against documentation.

It states that modules are tested against user requirements.

It only models the testing phase.

It specifies the test techniques to be used.

It includes the verification of designs.

Manual testing

Automation testing

Both

None

Test first approach

Test-driven development

Both A. & B.

None of the above

Phase building activity

Intermediate activity

End of Phase activity

Design activity

Support for the management of tests and the testing activities carried out

Interfaces to test execution tools

Quantitative analysis related to tests

Check for consistency and undefined requirements

None of the above

Budget, Test environment

Budget, Number of qualified test resources

Budget, Number of qualified test resources

None of the above

The data required for testing, the infrastructure requirements to manage the data as well as the methods for preparing test data, requirements, converters and sources

Details what types of tests must be conducted, what stages of testing are required and outlines the sequence and timing of tests

A testing goal. It is a statement of what the tester is expected to accomplish or validate during a testing activity. These guide the development of test cases and procedures

None of the above

Program is tested randomly sampling the input.

A black-box testing technique

Both A. and B.

None of the above.

Statement coverage

Condition coverage

Decision coverage

None of these

They are used to support multi-user testing.

They are used to capture and animate user requirements.

They are the most frequently purchased types of CAST tool.

They capture aspects of user behavior.

They are cheapest to find in the early development phases and the most expensive to fix in the latest test phases.

They are easiest to find during system testing but the most expensive to fix then.

Faults are cheapest to find in the early development phases but the most expensive to fix then.

Although faults are most expensive to find during early development phases, they are cheapest to fix then.