ISTQB Practice Questions Simulator - 2

The probability the negative event will occur

The potential loss or impact associated with the event

Both a and b

Neither a nor b

Use risk based analysis to find out which areas need to be tested

Use automation tool for testing

A and b

None of the above

Deviations from standards

Requirement defects

Design defects

Insufficient maintainability and incorrect interface specifications

All of the above

That you have tested every statement in the program

That you have tested every statement and every branch in the program

That you have tested every IF statement in the program

That you have tested every combination of values of IF statements in the program

Use risk based analysis to find out which areas need to be tested

Use automation tool for testing

A and b

None of the above

No, the problem is not with testers

No, the software is not ready for production

Both a & b

None of the above

Identifying defects

Fixing defects

1 and 2

None

Functional automation tools

Performance testing tools

Configuration management tools

None of the above

Test manager

Test engineer

Both A & B

Project Manager

Requires knowledge on the bug fixes and how it affect the system

Includes the area of frequent defects

Includes the area which has undergone many/recent code changes

All of the above

Test data

Test data plan

Test summary report

Test procedure plan

Schedules and deliverables

Hardware and software

Entry and exit criteria

Types of test cases

Reduces the time spent by the testers

Reduces the resources spent (hardware)

Mostly used in web testing

All of the above

Shows the number of newly discovered defects per unit time

Shows the number of open defects per unit time

Shows the cumulative total number of defects found up to this time

Any of these, depending on the company

Testers spend more energy early in the product trying to find bugs than preparingto do the rest of the project's work more efficiently

Managers might not realize that the testing effort is ineffective, late in the project,because they expect a low rate of bug finding, so the low rate achieved doesn'talarm them

It can increase the end-of-project pressure on testers to not find bugs, or to notreport bugs

All of the above

Work with the project's stakeholders early on to understand howrequirements might change so that alternate test plans and strategiescan be worked out in advance, if possible

Negotiate to allow only easily-implemented new requirements into theproject, while moving more difficult new requirements into futureversions of the application

Both a and b

None of the above

We can never be certain that the program is bug free

We have no definite stopping point for testing, which makes it easier for somemanagers to argue for very little testing

We have no easy answer for what testing tasks should always be required,because every task takes time that could be spent on other high importance tasks

All of the above

Desk checking

Debugging a program

A mutation error

Performance testing

Introducing mutations

Compliance testing

Disaster testing

Verifying compliance to rules

Functional testing

Ease of operations

The failure occurs only if you reach a statement taking the TRUE branch of an IF statement, and you got to the statement with a test that passed through the FALSE branch

The failure depends on the program's inability to handle specific data values, rather than on the program's flow of control

Both A and B

We are not required to test code that customers are unlikely to execute

Compliance testing

Disaster testing

Verifying compliance to rules

Functional testing

Ease of operations

Security failures were the result of untested parts of code

The development team achieved complete statement and branch coverage butmissed a serious bug in the MASPAR operating system

An error in the code was so obscure that you had to test the function with almostevery input value to find its two special-case failures

All of the above

Even though the numbers you look at appear better, to achieve these numbers, people are doing other aspects of their work much less well

We don't know how to measure a variable (our measurement is dysfunctional) and so we don't know how to interpret the result.

You are measuring the wrong thing and thus reaching the wrong conclusions

All of the above.

You have discovered every bug in the program

You have tested every statement, branch, and combination of branches in theprogram

You have completed every test in the test plan.

You have reached the scheduled ship date

Assess development plan and status

Develop the test plan

Test software design

Test software requirement