A role of a formal review is B. Moderator. A formal review is a type of static technique that involves a structured process of examining code or other software artifacts by a team of reviewers who follow predefined roles and rules. A formal review has four main phases: planning, preparation, meeting, and follow-up. A formal review has five main roles: author (the person who created the code or other software artifact under review), moderator (the person who leads and facilitates the review process), reviewer (the person who examines the code or other software artifact under review and provides feedback), scribe (the person who records the issues and outcomes of the review meeting), and manager (the person who monitors and controls the review process). A moderator is a key role in a formal review because he or she is responsible for planning, organizing, conducting, and reporting the review activities and ensuring that the review objectives are met. A detailed explanation of formal reviews can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 35-37.

Equivalence partitioning is best defined as an analysis technique that divides inputs into groups that are expected to exhibit similar behaviors. The idea is to reduce the number of test cases by selecting one representative value from each group or partition. Equivalence partitioning does not apply to time-related data classes only, but to any type of input data that can be divided into partitions. Equivalence partitioning is not a form of white-box testing, but a black-box testing technique. Equivalence partitioning is not a method to reduce test coverage, but a method to achieve test coverage more efficiently.

The process that ensures that all items of testware are identified, version controlled, tracked for changes, so that traceability can be maintained throughout the test process is D. Configuration management process. Configuration management is a process that establishes and maintains the integrity and consistency of all items of testware throughout the test process. Configuration management involves identifying, storing, controlling, tracking, and auditing all items of testware (such as test plans, test cases, test scripts, test data, test results, etc.) and their versions and changes. Configuration management helps to ensure that only authorized and approved items of testware are used for testing and that traceability can be maintained between them. A detailed explanation of configuration management can be found in  A Study Guide to the ISTQB® Foundation Level 2018 Syllabus , pages 101-102 1 .

The minimum number of test cases required to guarantee both 100% statement coverage and 100% decision coverage is 2. Statement coverage means that every statement in the code is executed at least once by the test cases. Decision coverage means that every possible outcome of each decision (such as if-else statements) is executed at least once by the test cases. To achieve both statement and decision coverage, we need to test two scenarios: one where X > Y and one where X < = Y. This will ensure that all statements and decisions are covered by the test cases. A detailed explanation of statement and decision coverage can be found in  A Study Guide to the ISTQB® Foundation Level 2018 Syllabu s , pages 61-67 1 .

Performance, Load, Stress. Performance testing is a type of non-functional testing that measures how well the system performs under various conditions, such as response time, throughput, resource utilization, etc. Load testing is a type of performance testing that simulates a high volume of user requests or transactions on the system and measures its behavior under normal and peak load conditions. Stress testing is a type of performance testing that simulates extreme or abnormal conditions on the system and measures its behavior under stress or overload conditions. These test types would help verify the requirements such as minimum number of enquiries per hour, availability, and response time under peak loads. A detailed explanation of performance, load, and stress testing can be found in  Software Testing Foundations: A Study Guide for the Certified Tester Exam , pages 187-191 3 .

A limitation in the use of static analysis tools is C. Static analysis tools always generate large numbers of warning messages when applied to new code, even if the code meets coding standards. Static analysis tools are tools that analyze the code or other software artifacts without executing them, and report any defects, errors, vulnerabilities, or violations of coding standards or conventions. Static analysis tools can help to improve the quality and maintainability of the code or other software artifacts. However, static analysis tools also have some limitations, such as generating large numbers of warning messages when applied to new code, even if the code meets coding standards or conventions. This can make it difficult for developers or testers to identify and prioritize the most important or critical issues to fix or address. A detailed explanation of static analysis tools can be found in  A Study Guide to the ISTQB® Foundation Level 2018 Syllabus , pages 109-110 1 .

Screen-dialog flows are sequences of screens and dialogs that represent the user interface and interaction of a system.  Use case testing is a technique that uses use cases as a test ba sis to derive test cases 1 .  A use case is a description of interactions between actors and a system to achieve a go al 1 . Use case testing is the most effective technique in testing screen-dialog flows, as it can capture the user requirements, scenarios, and expected outcomes of the system.  Boundary value testing is a technique that uses boundary values as a test basis to derive test cases 1 .  A boundary value is an input value or output value on the edge of an equivalence partition or at the smallest or largest value of a range 1 . Boundary value testing is not the most effective technique in testing screen-dialog flows, as it is more suitable for testing numerical inputs and outputs.  State ment testing and coverage is a technique that uses statements in the source code as a test basis to measure the coverage achieved by a test suite 1 .  A statement is a minimal executable unit of source code 1 . Statement testing and coverage is not the most effective technique in testing screen-dialog flows, as it is more suitable for testing the internal logic and structure of the code.  Stat e transition testing is a technique that uses state transition diagrams as a test basis to derive test cases 1 .  A s tate transition diagram shows the states of a system and the transitions between them triggered by events or conditions 1 . State transition testing is not the most effective technique in testing screen-dialog flows, as it is more suitable for testing systems that have complex or dynamic behavior based on different states.

The effective ways to improve the communication and relationship between testers and others are A. a and b. Communicating factual information in a constructive way and trying to understand how the other person feels and why they react the way they do are both important skills for testers to have. Testers often have to report defects and problems that may not be well received by developers or users. Therefore, testers should communicate in a clear, objective, and respectful manner, avoiding personal attacks or blame. Testers should also empathize with the other person’s perspective and emotions, and try to resolve any conflicts or misunderstandings in a positive way. A detailed explanation of communication skills for testers can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus] , pages 107-108.

The Cambrian Pullman Express has special ticketing requirements represented by the partial decision table below. The decision table has six columns representing six rules and eight rows representing eight conditions or actions. The table is filled with “Y” and “N” values indicating whether a particular condition is met for a particular rule.

!decision table

Carol has a student railcard and is travelling on a Flexible Standard Class ticket. James has a senior railcard and is travelling on a super saver ticket. The question asks which of the options represents the correct actions for these two test cases. To answer this question, we need to find the matching rule for each test case and then look at the corresponding actions. For Carol, the matching rule is rule 2, as she has a student railcard (Y) and a Flexible Standard Class ticket (Y). The actions for rule 2 are: OK to travel (Y), eligible to upgrade (Y), and concessionary fare (N). Therefore, Carol is OK to travel and eligible to upgrade, but not entitled to a concessionary fare. For James, the matching rule is rule 6, as he has a senior railcard (Y) and a super saver ticket (N). The actions for rule 6 are: OK to travel (N), eligible to upgrade (N), and concessionary fare (N). Therefore, James cannot use the service, is not eligible to upgrade, and is not entitled to a concessionary fare. Among the options given in this question, only A correctly represents these actions. A says that Carol is eligible to upgrade and James cannot use the service. Therefore, A is the correct answer.

The test execution schedule should take into account the prioritization and other constraints given in the question. The first activity is to run any re-tests, followed by the regression test script. Users have supplied their priority order to tests. Therefore, the test execution schedule should start with the re-test defect no 52, which is shown in the image as a table with 9 rows and 4 columns. The table is titled “Re-test defect no 52”. The columns are labeled: “#”, “Description”, “Priority”, “Note”, “Re-test”. The table is populated with data about different tasks and their priority and notes. The tasks are related to sales figures and account administration. The table is in black and white. The re-test defect no 52 has three tasks: c, a, and d, which have priority 1, 2, and 3 respectively. Therefore, the test execution schedule should start with c, followed by a, and then d. After that, the regression test script should be run, which is task e. Then, the remaining tasks should be run according to the user priority order: b, g, i, h, and f. Therefore, the test execution schedule is c, a, d, e, b, g, i, h, and f.