Testing usability and performance in a realistic pre-production environment helps validate non-

functional requirements under near-live conditions.

“Evaluating non-functional quality characteristics such as... performance efficiency... and usability” is

a core part of test types.

“Acceptance testing... focused on verifying a new feature against its acceptance criteria and

validating that a new feature satisfies the users’ needs” can also include non-functional testing like

usability and performance.

Creating a resource allocation strategy is essential when managing a split team between offshore

and onshore teams. The Test Manager is responsible for ensuring coordination, workload balancing,

and seamless communication across geographically dispersed teams. This aligns with test planning

activities which include “making decisions about the people and other resources required to perform

the various test activities” .

The best option to address this scenario is to leverage the development team to fill any knowledge

gaps in the in-house tool. This option allows the test team to reuse the existing performance test

suite and avoid the risks and costs of switching to a new tool or excluding performance testing

altogether. The development team can provide support and guidance to the test team on how to use

and modify the in-house tool, since it is written in the same programming language as the product

itself. This option also preserves the intellectual property of the organization and does not expose

the in-house tool to the open source community. ISTQB Advanced Level Test Manager

SyllabusAdvanced Software Testing - Vol. 2 Reference:

ISTQB Advanced Level Test Manager Syllabus

Advanced Software Testing - Vol. 2, 2nd Edition

:

According to the tool lifecycle model, the evolution stage is when the tool is adapted to new

requirements or environments, such as a new operating system. This stage involves modifying the

tool to meet the changing needs of the users and the system. The evolution stage is followed by the

retirement stage, when the tool is no longer used or supported. Tool Lifecycle ModelSoftware Testing

Tools Reference:

Work with performance and monitoring tools in finance and operations apps

Software Testing Tools: A Comprehensive Guide

:

The graph indicates that a significant portion of risks, 29%, have not been mitigated, which suggests

that these are either failed tests or other discovered failures. This level of unmitigated risk puts the

project at risk, as it implies that there are still substantial issues that need to be addressed.

Reference:

The ISTQB Advanced Level Test Manager documents outline the importance of risk-based testing and

the interpretation of residual risk graphs. These graphs are used to communicate the current status

of risk mitigation efforts in the project, and a high percentage of unmitigated risks is a clear indicator

of potential problems1.

The correct answer is A. Can be used to identify test coverage gaps. This is because test conditions

are the items or events of a component or system that will be verified by one or more test cases.

Specifying test conditions at a detailed level can help to identify test coverage gaps, which are the

areas or aspects of the component or system that are not covered by the test conditions or test

cases. By identifying test coverage gaps, the test team can ensure that the testing is complete and

consistent with the test objectives and scope. Test Conditions - ISTQB not-for-profit

association Reference: Certified Tester Advanced Level Test Manager (CTAL-TM) - ISTQB not-for-profit

association, ISTQB Test Manager Certification - ISTQB Exams Worldwide - ISTQB Official

Registration, Test Conditions - ISTQB not-for-profit association

Test planning involves identifying resources, responsibilities, scheduling, estimating efforts, and

allocating resources. It is an early phase activity, not something that waits until all risks are

identified.

"Test planning activities include defining the objectives of testing, the scope of the test effort, the

risks, the resources required, test levels to be applied, and the schedule of testing activities."

(Source: ISTQB Advanced Level Test Manager Syllabus 2012, Section 2.2)

Thus, Option A correctly summarizes test planning.

: