Explanation / Rationale

a) Is correct. A crash is clearly noticeable by the user
b) Is not correct. This is a defect, not a failure since there is something wrong in the code. It may not result in a visible or noticeable failure, for example if the changes in the source code file are only in comments
c) Is not correct. The use of wrong input variables may not result in a visible or noticeable failure, for example if nobody uses this particular algorithm; or if the wrong input variable has a similar value to the correct input variable; or if the FALSE result of the algorithm is not used
d) Is not correct. This type of fault will not necessarily lead to a failure; for example, if no one uses this special algorithm

Explanation / Rationale

The level of risk will be determined by the likelihood of an adverse event happening and the impact (the harm) from that event.

Thus:
a) Is not correct
b) Is not correct
c) Is not correct
d) Is correct

Explanation / Rationale

a) Is not correct. Reviews reduce, not increase, the total cost of quality
b) Is not correct. Increasing velocity is a sign of increasing development productivity overall, not just testing, so B only partially applies
c) Is correct. Velocity is a way of measuring productivity in Agile development
d) Is not correct. The benefit mentioned here has to do with increasing overall development team productivity

Explanation / Rationale

The possible mappings of points 1 to 4 can be justified as follows:

1. Approach 3 is analytical: Risk-based testing is an example of an analytical approach, where tests are designed and prioritized based on the level of risk
2. Approach 2 is standard-compliant: The control algorithms is checked against industry-specific standard of the energy saving regulation.
3. Approach 4 is consultative: This type of test strategy is driven primarily by the advice, guidance, or instructions of stakeholders, business domain experts, or technology experts, who may be outside the test team or outside the organization itself
4. Approach 1 is reactive: Exploratory testing is a common technique employed in reactive strategies, whereby the explorative testing is assigned to the experience-based testing category

Thus:
a) Is not correct
b) Is correct
c) Is not correct
d) Is not correct

Explanation / Rationale

Each transition must be traversed at least once. To do so, the first test can cover the happy path, a successful purchase, the next test cancels, or timeout from waiting for pumping, the next test cancels, or timeout from waiting for fuel type, and the last test the insertion of an invalid credit card. While the order is immaterial, fewer than four tests fail to cover one of the transitions inbound to waiting for customer or violates the rules about where a test starts or ends. More than four tests include tests that re-traverse already-covered transitions.

Thus:
a) Is correct
b) Is not correct
c) Is not correct
d) Is not correct

Explanation / Rationale

a) Is not correct. Quality should be the responsibility of everyone working on the project and not the sole responsibility of the test team
b) Is not correct. First, it is not a benefit if an external test team does not meet delivery deadlines, and second, there is no reason to believe that external test teams will feel they do not have to meet strict delivery deadlines
c) Is not correct. It is bad practice for the test team to work in complete isolation, and we would expect an external test team to be concerned with changing project requirements and communicate well with developers
d) Is correct. Specifications are never perfect, meaning that assumptions will have to be made by the developer. An independent tester is useful in that they can challenge and verify the assumptions and subsequent interpretation made by the developer

Explanation / Rationale

a) Is correct. Test management tools support the activities associated with test manager including metrics
b) Is not correct. Static code analysis metrics would have to do with the code only, not testing as a whole
c) Is not correct. These tools report on test basis coverage and code coverage only, not testing as a whole
d) Is not correct. Model-Based testing tools focus on one specific area, not testing as a whole

Explanation / Rationale

a) Is correct. This is an objective listed
b) Is not correct. This is debugging
c) Is not correct. This is an activity within the test execution group of activities within the test process
d) Is not correct. This is part of debugging

Explanation / Rationale

a) Is not correct. If there was no agreement on targets, it is impossible to reach the targets. Since this situation can´t occur, this is not a scenario happening in reality
b) Is not correct. The test case is objectively wrong, since under these conditions no bonus is paid because the agreed target was not reached
c) Is not correct. There was no agreement on targets, it is impossible to reach the targets. Since this situation can´t occur, this is not a scenario happening in reality
d) Is correct. The test case describes the situation that the too short period of employment and the non-fulfilment of the agreed target leads to non-payment of the bonus. This situation can occur in practice but is missing in the decision table

Explanation / Rationale

There are three equivalence partitions, with the boundaries as shown:

• Invalid too low (0.4 and below)
• Valid (0.5 to 25.0)
• Invalid too high (25.1 and above)

Thus:
a) Is not correct. Only two of the equivalence partitions are covered in this set of tests
b) Is not correct. Each of those four boundary values are included in this set of tests, but the question asked for equivalence partition coverage with minimal tests, so either 0.5 or 25.0 should be dropped
c) Is correct. Each of these three equivalence partitions are covered in this set of tests
d) Is not correct. Only one of those equivalence partitions is covered by this test

Explanation / Rationale

a) Is correct. One of the major objectives of testing
b) Is not correct. Validation of the project plan would be a project management activity
c) Is not correct. Contradiction to principle #2; complete/exhaustive testing is not possible
d) Is not correct. “Comparing actual results with expected results” is a test performing activity, but not a test objective

Explanation / Rationale

a) Is not correct. During planning it is decided whether checklists are used. The preparation of the checklists is not part of the planning. In addition, the reviewers are neither involved in the planning, nor responsible for the creation of the checklists
b) Is not correct. During issue communication, any potential defects that have been identified in the individual review are communicated. The completion of checklists by the reviewers already takes place, if at all, during individual review
c) Is not correct. During review session, the reviewers communicate any potential defects of the work product that they did identify during the individual review. Defect reports are only created during the fixing and reporting activity
d) Is correct. Initiating the review (“Kick-off”) involves distributing the work product and other materials, like checklists

Explanation / Rationale

There are three equivalence partitions, with the boundaries as shown:

• Invalid too low (0.4 and below)
• Valid (0.5 to 25.0)
• Invalid too high (25.1 and above)

Thus:
a) Is not correct. None of those four boundary values are included in this set of tests. These tests do cover the equivalence partitions
b) Is not correct. All these four boundary values are included in this set of tests, but two additional values are included, one for each boundary. These are the values associated with three-point boundary value analysis
c) Is correct. Each of those four two-point boundary values are included in this set of tests
d) Is not correct. These four values are all included in the valid partition

Explanation / Rationale

a) Is not correct. Although the description of regression testing is largely correct, the description of confirmation testing (which should be testing a defect has been fixed) is not correct
b) Is correct. The descriptions of both confirmation and regression testing match the intent of those in the syllabus
c) Is not correct. Although the description of regression testing is largely correct, the description of confirmation testing (re-running all previously run tests to get the same results) is not correct, as the purpose of confirmation testing is to check that tests that previously failed now pass (the fix worked)
d) Is not correct. Although the description of confirmation testing is largely correct, the description of regression testing (re-running tests that previously failed) is not correct (this is a more detailed description of confirmation testing)

Explanation / Rationale

The following valid equivalence partitions can be identified:

1. Up to 1000 - Couch Potato!
2. Above 1000, up to 2000 - Lazy Bones!
3. Above 2000, up to 4000 - Getting There!
4. Above 4000, up to 6000 - Not Bad!
5. Above 6000 - Way to Go!

The sets of test inputs therefore cover the following partitions:
a) Is not correct. 0 (1), 1000 (1), 2000 (2), 3000 (3), 4000 (3) – 3 partitions (out of 5)
b) Is not correct. 1000 (1), 2001 (3), 4000 (3), 4001 (4), 6000 (4) – 3 partitions (out of 5)
c) Is not correct. 123 (1), 2345 (3), 3456 (3), 4567 (4), 5678 (4) – 3 partitions (out of 5)
d) Is correct. 666 (1), 999 (1), 2222 (3), 5555 (4), 6666 (5) – 4 partitions (out of 5)

Explanation / Rationale

a) Is not correct. ‘Beware of the pesticide paradox’ is concerned with re-running the same tests and their fault-finding effectiveness decreasing
b) Is not correct. This testing principle is concerned with performing testing differently based on the context (e.g., games vs safety-critical)
c) Is not correct. This testing principle is concerned with the difference between a tested and fixed system and a validated system. No ‘errors’ does not mean the system is fit for use
d) Is correct. If clusters of defects are identified (areas of the system containing more defects than average), then testing effort should be focused on these areas

Explanation / Rationale

Test 01.001 must come first, followed by 01.002, to satisfy dependencies. Afterwards, 01.004 and 01.003 should be run in either order, followed by 01.005, to satisfy priority.
Thus:
a) Is not correct
b) Is correct
c) Is not correct
d) Is not correct

Explanation / Rationale

a) Is not correct. Structure-based, or white-box techniques are based on an analysis of the architecture, detailed design, internal structure, or the code of the test object
b) Is correct. Behavior-based, or black-box techniques are based on an analysis of the appropriate test basis (e.g., formal requirements documents, specifications, use cases, user stories, or business processes), which describe functional and non-functional behavior
c) Is not correct. Experience-based techniques leverage the experience of developers, testers, and users to determine what should be tested
d) Is not correct. Error guessing is a type of experience-based testing, which is not black-box

Explanation / Rationale

a) Is not correct. Traceability will allow existing test cases to be linked with updated and deleted requirements (although there is no support for new requirements), but it will not help with the automation of maintenance testing
b) Is correct. If all test cases are linked with requirements, then whenever a new test case (with traceability) is added, it is possible to see if any previously uncovered requirements are covered by the new test case
c) Is not correct. Traceability between the test basis and test artifacts will not provide information on which testers found high-severity defects, and, even if this information could be determined, it would be of limited value
d) Is not correct. Traceability can help with identifying test cases affected by changes, however areas impacted by side-effects would be the focus of regression testing

Explanation / Rationale

a) Is not correct. While the given statement is true, the explanation is not. The relationship between statement and decision coverage is misrepresented
b) Is correct. Since any test case will cause the outcome of the “if” statement to be either TRUE or FALSE, by definition we achieved 50% decision coverage
c) Is not correct. A single test case can give more than 25% decision coverage, this means according to the statement above always 50 % decision coverage
d) Is not correct. The statement is specific and always true, because each test case achieves 50 % decision coverage

Explanation / Rationale

a) Is correct. This explains that each use case specifies some behavior that a subject can perform in collaboration with one or more actors. It also (later) explains that tests are designed to exercise the defined behaviors (basic, exceptional and errors)
b) Is not correct. Use cases normally specify requirements, and so do not ‘include’ the components that will implement them
c) Is not correct. Tests based on use cases do exercise interactions between the actor and the system, but they are focused on the functionality and do not consider the ease of use of user interfaces
d) Is not correct. Tests do cover the use case paths through the use case, but there is no concept of decision coverage of these paths, and certainly not of business process flows

Explanation / Rationale

a) Is not correct. The benefits are not when creating regressions tests, more in executing them
b) Is not correct. This is done by configuration management tools
c) Is not correct. This needs specialized tools
d) Is correct. Reduction in repetitive manual work (e.g., running regression tests, environment set up/tear down tasks, re-entering the same test data, and checking against coding standards), thus saving time

Explanation / Rationale

Proposed test case covers all five possible single valid transitions in the given state diagram (S1->S2, S2->S1, S2->S3, S3->S2, and S3->S1).

Thus:
a) Is not correct. Because no invalid transitions are covered
b) Is correct. Because all valid transitions are covered
c) Is not correct. Because all valid transitions are covered
d) Is not correct. Because the test cases do not have pairs of transitions specified

Explanation / Rationale

a) Is not correct. Both developers and testers gain from experience
b) Is correct. Developers are often more interested in designing and building solutions than in contemplating what might be wrong with those solutions
c) Is not correct. Both developers and testers should be able to communicate well
d) Is not correct. Testers shall focus on the quality, not on the quantity

Explanation / Rationale

a) Is not correct. Tester and developer are NOT roles in a formal review
b) Is not correct. Developer is NOT a role in a formal review
c) Is not correct. Designer is NOT a role in a formal review
d) Is correct. See reasons from incorrect answers

Explanation / Rationale

a) Is not correct. This is the Glossary definition of quality assurance
b) Is correct. This is the Glossary definition of quality
c) Is not correct. This is the Glossary definition of security
d) Is not correct. This is the Glossary definition of cost of quality

Explanation / Rationale

Considering the attributes:

• There is a role of a scribe – specified for walkthroughs, technical reviews, and inspections; thus, the reviews being performed cannot be informal reviews
• The purpose is to detect potential defects – the purpose of detecting potential defects is specified for all types of review.
• The review meeting is led by the author – this is not allowed for inspections and is typically not the author for technical reviews, but is part of walkthroughs, and allowed for informal reviews
• Reviewers find potential issues by individual review - all types of reviews can include individual review (even informal reviews)
• A review report is produced - all types of reviews can produce a review report, although it would be less likely for an informal review

Thus:
a) Is not correct
b) Is correct
c) Is not correct
d) Is not correct

Explanation / Rationale

The correct pairings of examples to entry and exit criteria are:

• Entry criteria

o (3) The trading performance test environment has been designed, set-up and verified – example of the need for a test environment to be ready before testing can begin
o (5) The autopilot design specifications have been reviewed and reworked – example of the need for the test basis to be available before testing can begin
o (6) The tax rate calculation component has passed unit testing – example of the need for a test object to have met the exit criteria for a prior level of testing before testing can begin

• Exit criteria

o (1) The original testing budget of $30,000 plus contingency of $7,000 has been spent – example of spending the testing budget being a signal to stop testing
o (2) 96% of planned tests for the drawing package have been executed and the remaining tests are now out of scope – example of all the planned tests being run being a signal to stop testing (normally used alongside the exit criteria on outstanding defects remaining)
o (4) Current status is no outstanding critical defects and two high-priority ones – example of the number of outstanding defects achieving a planned limit being a signal to stop testing (normally used alongside the exit criteria on planned tests being run).

Thus:
a) Is not correct
b) Is not correct
c) Is not correct
d) Is correct

Explanation / Rationale

a) Is not correct. See reason from correct answer
b) Is not correct. See reason from correct answer
c) Is correct. This is a case where the requirement gives an enumeration of discrete values. Each enumeration value is an equivalence class by itself; therefore, each will be tested when using equivalence partitioning test technique
d) Is not correct. See reason from correct answer

Explanation / Rationale

a) Is not correct. The programmer appears to be performing unit testing on their own code
b) Is not correct. Code coverage is useful for unit testing, but it is not a tester mindset
c) Is not correct. The programmer’s mindset included contemplating what might be wrong with the code, but that is not a tester’s mindset
d) Is correct. This tester mindset, attention to detail, will help programmers find defects during unit testing

Explanation / Rationale

The correct pairing of test activities and tasks is:

A. Test design – (2) Identifying test data to support the test cases
B. Test implementation – (3) Prioritizing test procedures and creating test data
C. Test execution – (4) Analyzing discrepancies to determine their cause
D. Test completion – (1) Entering change requests for open defect reports

Thus:
a) Is correct
b) Is not correct
c) Is not correct
d) Is not correct

Explanation / Rationale

a) Is not correct. Statement coverage is a measure of the proportion of executable statements exercised by tests. The number of executable statements is often close to the number of lines of code minus the comments, but this option only talks about the number of lines of code exercised and not the proportion exercised
b) Is correct. Statement coverage is a measure of the proportion of executable statements exercised by tests (normally presented as a percentage)
c) Is not correct. Statement coverage is a measure of the percentage of executable statements exercised by tests, however many of the lines of source code are not executable (e.g., comments)
d) Is not correct. Statement coverage is a measure of the proportion of executable statements exercised by tests. This option only talks about the number of executable statements exercised and not the proportion (or percentage) exercised

Explanation / Rationale

a) Is not correct. Testing is context dependent, regardless of it being manual or automated (principle #6), but does not result in detecting a decreasing number of faults as described above
b) Is not correct. Exhaustive testing is impossible, regardless of the amount of effort put into testing (principle #2)
c) Is correct. Principle #5 says “If the same tests are repeated over and over again, eventually these tests no longer find any new defects. To detect new defects, existing tests and test data may need changing, and new tests may need to be written.” Automated regression testing of the same test cases will not bring new findings
d) Is not correct. ”Defect cluster together” (principle #4). A small number of modules usually contain most of the defects, but this does not mean that fewer and fewer defects will be found

Explanation / Rationale

a) Is not correct. While this information is useful for developers, it does not provide managers with a sense of the impact on product quality
b) Is not correct. This summary does not provide developers or managers with the necessary information and attacks the developers
c) Is not correct. This summary does not provide developers or managers with the necessary information and attacks the developers
d) Is correct. This summary gives a good sense of the failure and its impact

Explanation / Rationale

a) Is not correct. Static testing does not involve execution of the test object
b) Is not correct. Some static tests involve the use of a tool, especially static analysis, but reviews (such as the activity described here) do not necessarily involve the use of a tool
c) Is not correct. The review activity described here is part of a static test, but defects found in static tests are usually cheaper than those found in dynamic testing
d) Is correct. Static testing does not involve execution of the test object

Explanation / Rationale

a) Is not correct. One too few (see the four correct partitions in the correct answer)
b) Is not correct. One too much (see the four correct partitions in the correct answer)
c) Is not correct. Two too few (see the four correct partitions in the correct answer)
d) Is correct. The 4 equivalence partitions correspond to the description in the question, i.e., at least one test case must be created for each equivalence partition:

1. Equivalence partition: 0 ≤ employment time ≤ 2
2. Equivalence partition: 2 < employment time < 5
3. Equivalence partition: 5 ≤ employment time ≤ 10
4. Equivalence partition: 10 < employment time

Explanation / Rationale

a) Is not correct. Selection of tools is a test manager task
b) Is correct. See reasons from incorrect answers
c) Is not correct. The tester does not decide on the release of the test object
d) Is not correct. The tester specifies the test cases, the test manager does the prioritization

Explanation / Rationale

a) Is not correct. While recognizing different kinds of failures is a benefit of tester independence, in the scenario here no code yet exists that can fail, and the problem is that the developer and product owner are both assuming different things about the acceptance criteria
b) Is not correct. Developers losing a sense of responsibility for quality is a drawback, not a benefit
c) Is not correct. While the effect of the discovery of this disagreement is the earlier removal of the defect, prior to coding, defects can be discovered early by various people, not just independent testers
d) Is correct. Challenging stakeholder assumptions is a benefit of tester independence, and here the developer and product owner are both assuming different things about the acceptance criteria

Explanation / Rationale

a) Is not correct. Statement testing exercises the executable statements in the code, which might result in the absence of certain greetings not being tested
b) Is not correct. Unless the test charter specifically mentioned testing both the presence and the absence of each type of greeting, coverage can be difficult to assess for an exploratory test
c) Is not correct. State transition testing is useful for situations where the test object responds differently to an input depending on current conditions or previous history, but in this case the test object must decide whether the current date matches a particular milestone and thus whether to display the relevant greeting
d) Is correct. Decision testing involves test cases that follow the control flows that occur from a decision point, which in this case would be deciding whether a greeting should or should not be given

Explanation / Rationale

a) Is not correct. Exploratory testing is often carried out when timescales are short, so making in-depth investigations of the background of the test object is unlikely
b) Is correct. Glossary definition
c) Is not correct. Based on the Glossary definition of session-based testing, but with test execution replaced by test analysis
d) Is not correct. Glossary definition of experience-based testing