Chapter 5 - Part 1

Front

What is risk-based testing?

Back

A test approach which test activities are selected, prioritized, and managed based on risk analysis and risk control.

Answer explanation

According to the syllabus: The test approach, in which test activities are selected, prioritized, and managed based on risk analysis and risk control, is called risk-based testing. (page 50)

Front

The level of risk is determined by which of the following? Likelihood and impact

Back

Likelihood and impact

Answer explanation

Risk is a potential event, hazard, threat, or situation whose occurrence causes an adverse effect. A risk can be characterized by two factors:

• Risk likelihood – the probability of the risk occurrence (greater than zero and less than one)

• Risk impact (harm) – the consequences of this occurrence

These two factors express the risk level, which is a measure for the risk. The higher the risk level, the more important is its treatment.

Front

Which of the following is the characteristic of a metrics-based approach for test estimation? Budget which was used by a previous similar test project, Overall experience collected in interviews with test managers, Estimation of effort for test automation agreed in the test team, Average of calculations collected from business experts

Back

Budget which was used by a previous similar test project

Answer explanation

A metrics-based approach for test estimation typically uses historical data from past projects. This could manifest in a variety of metrics such as past budgets, durations, team sizes, or issue counts.

Front

The ISTQB Foundation Syllabus establishes a fundamental test process where test planning occurs early in the project, while test execution occurs at the end. Which of the following elements of the test plan, while specified during test planning, is assessed during test execution? Exit criteria, Entry criteria, Test tasks, Test team training

Back

Exit criteria

Front

Consider the following exit criteria which might be found in a test plan:
I. No known customer-critical defects.
II. All interfaces between components tested.
III. 100% code coverage of all units.
IV. All specified requirements satisfied.
V. System functionality matches legacy system for all business rules.
Which of the following statements is true about whether these exit criteria belong in an acceptance test plan?

Back

Only statements I, IV, and V belong in an acceptance test plan.

Answer explanation

An acceptance test plan focuses on validating whether the system meets business requirements and is ready for deployment. The relevant exit criteria should align with user needs, functional expectations, and business goals.

II. All interfaces between components tested. -> relevant to integration testing

III. 100% code coverage of all units. -> typically a unit testing criterion

Front

In prioritizing what to test, the MOST important objective is to: Obtain good test coverage, Test high risk areas, Find as many faults as possible, Test whatever is easiest to test

Back

Test high risk areas

Front

Your team uses the three-point estimation technique to estimate the test effort for a new high-risk feature. The following estimates were made:

• - most optimistic estimation: 4 person-hours
• - most likely estimation: 13 person-hours
• - most pessimistic estimation: 10 person-hours

What is the final estimation?

Back

11 person-hours

Answer explanation

E = (a + m*4 + b)/6 = (4 + 13*4 + 10)/6 = 11

Front

Which is the difference between a product risk and a project risk?

Back

Project risks are the risks that surround the project's capability to deliver its objectives; product risks are potential failure areas in the software or system.

Front

Which of the following would NOT normally form part of a test plan? Test environment requirements, Test basis, Test procedures, Test objectives

Back

Test procedures

Front

You are working as a tester on a project to develop a point-of-sales system for grocery stores and other similar retail outlets. Which of the following is a product risk for such a project? An excessively high number of defect fixes fail during confirmation testing, The arrival of a more reliable competing product on the market, Delivery of an incomplete test release to the first cycle of the system test, Failure to accept allowed credit cards

Back

Failure to accept allowed credit cards

Answer explanation

A product risk refers to potential issues in the software itself, affecting its functionality, security, or usability. The others are related to Project risks