Certified Tester Foundation Level - ISTQB Foundation Sample Quiz 1

Explanation / Rationale

Explanation / Rationale

Explanation / Rationale

Explanation / Rationale

Explanation / Rationale

Explanation / Rationale

The ‘exhaustive testing is impossible’ principle is concerned with the fact that it is not feasible to test every possible variation of test inputs in all different circumstances, except in trivial cases. Instead, testing utilizes test techniques, test case prioritization, and risk-based testing to sample from the set of possibilities and focus testing efforts.

Explanation / Rationale

Explanation / Rationale

Explanation / Rationale

Explanation / Rationale

Explanation / Rationale

Explanation / Rationale

Explanation / Rationale

Explanation / Rationale

Considering each of the listed task descriptions:

1. The quality characteristics to be evaluated and the exit criteria are selected - (Planning (C): Defining the review scope, purpose, work product to be reviewed, quality characteristics to be evaluated, areas of focus, exit criteria, supporting information such as standards, effort, and timeframes.)

2. Everyone has access to the work product - (Review initiation (B): Ensuring all participants have access to the work product and necessary resources, and clarifying their roles and responsibilities.)

3. Anomalies are identified in the work product - (Individual review (A): Evaluating the work product's quality, identifying and logging anomalies, recommendations, and questions using review techniques like checklist-based and scenario-based reviewing.)

4. Anomalies are analyzed and discussed - (Communication and analysis (D): Analyzing and discussing each anomaly, determining its status, ownership, and required actions, and making review decisions, normally in a meeting. This could include determining the need for a follow-up review.)

Thus:

Considering each of the listed roles:

1. Scribe (or Recorder) - responsible for gathering feedback from reviewers and documenting review information, such as decisions made, and any new anomalies identified during the review meeting. (Records review information, such as decisions and new anomalies found during the review meeting - B)

2. Review Leader - responsible for overseeing the review process, such as selecting the review team members, scheduling review meetings, and ensuring that the review is completed successfully.
(Takes overall responsibility for the review such as organizing when and where the review will take place - D)

3. Facilitator (or Moderator) - responsible for ensuring that the review meetings run effectively, including managing time, mediating discussions, and creating a safe environment where everyone can voice their opinions freely. (Ensures the effective running of review meetings and the setting up of a safe review environment - A)

4. Manager - responsible for deciding what needs to be reviewed and allocating resources, such as staff and time, for the review. (Decides what is to be reviewed and provides resources, such as staff and time for the review - C)

Explanation / Rationale

N/A

Explanation / Rationale

Explanation / Rationale

Explanation

N/A

Exploratory testing is useful when there are few or inadequate specifications or there is significant time pressure on the testing.
Exploratory testing is also useful to complement other more formal test techniques.
Exploratory testing will be more effective if the tester is experienced, has domain knowledge and has a high degree of essential skills, like analytical skills, curiosity and creativeness.

Explanation / Rationale

The domain for the password length has three equivalence partitions:
=> passwords too short {0, 1, …, 4, 5}
=> passwords OK {6, 7, …, 11, 12}
=> passwords too long {13, 14, …}

To achieve full coverage for 3-value BVA we need to test the following values:
=> 0, 1, 4, 5, 6, 7, 11, 12, 13, 14.

Since 2-value BVA is already covered, this means that we have already tested the passwords of length:
=> 0, 5, 6, 12 and 13.

This means that the additional lengths that need to be covered to move from 2-value to 3-value are:
=> 1, 4, 7, 11 and 14.

There are five columns in the decision table. Each test case covers one of them.

TC1 and TC2 both cover Rule 4
TC3 and TC4 both cover Rule 2
TC5 covers Rule 5

So, these five test cases cover three out of five columns, achieving a coverage of (3/5)*100% = 60%.

Branch testing is a white-box test technique in which the coverage items are branches.

A branch is a transfer of control between two nodes in the control flow graph, which shows the possible sequences in which source code statements are executed in the test object. Each transfer of control can be either unconditional (i.e., straight-line code) or conditional (i.e., a decision outcome).

Coverage is measured as the number of branches exercised by the test cases divided by the total number of branches, and is expressed as a percentage.

N/A

According to the dependencies, SEARCH tests must be executed first, then VIEW tests, then ADD tests and, at the end, ORDER tests. Within each of these groups the order is determined by the priorities of the test cases.

So, TC1 must be executed first, then TC2, then TC4 followed by TC3, and then TC5 as the last one.
So, the ordering is: TC1, TC2, TC4, TC3, TC5.

N/A

The average development effort is $900,000 and the average test effort is $90,000 (calculated from the four projects).

The average test-to-development effort ratio is 1:10 ($90,000 : $900,000), which means that historically, on average, the test effort is 10% of the development effort.

So if the development effort is estimated to be $800,000, the estimated test effort is estimated as:

10% * $800,000 = 0.1 * $800,000 = $80,000.

N/A

Considering each of the listed risks and their mitigations:

1. Long system responses (1) can be tested in performance testing (B)
2. Changes of consumers’ preferences (2) are usually out of our control, so usually we accept this risk (A)
3. Flooding of the server room (3) can cause significant loss, so we should transfer the risk, e.g., by buying an insurance policy (D)
4. That patients above a certain age receive inaccurate reports (4) suggests a potential boundary problem, which can be effectively detected with techniques like BVA (C)

N/A

N/A

N/A

N/A

Considering each of the listed tool categories and their descriptions:

A. Static testing tools – support the tester in performing reviews and static analysis (4)
B. Tools supporting scalability and deployment standardization – For example, virtual machines, containerization tools (3)
C. DevOps tools – support the DevOps delivery pipeline, workflow tracking, automated build process(es), continuous integration/continuous delivery (CI/CD) (1)
D. Collaboration tools – facilitate communication (2)