Explanation / Rationale

a) Is correct. If the expected security features are not supported by the system architecture, then the system could be seriously flawed. As the system being produced is the problem here, it is a product risk
b) Is not correct. If the developers run over budget, or run out of time, that is a problem with the running of the project – it is a project risk
c) Is not correct. If the test cases do not provide full coverage of the requirements, this means the testing may not fulfil the requirements of the test plan – it is a project risk
d) Is not correct. If the test environment is not ready, this means the testing may not be done, or it may have to be done on a different environment and it is impacting how the project is run – it is a project risk

Explanation / Rationale

Glossary defines the following tests as:

• Test suite: “A set of test scripts or test procedures to be executed in a specific test run.” (1A)
• Test case: “A set of preconditions, inputs, actions (where applicable), expected results and post conditions, developed based on test conditions” (2C)
• Test script: “A sequence of instructions for the execution of a test” (3B)
• Test charter: “Documentation of test activities in session-based exploratory testing” (4D)

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

Explanation / Rationale

a) Is not correct. Contradiction to principle 3: “Early testing saves time and money”
b) Is correct. This is one objective of testing
c) Is not correct. Principle #2 states that exhaustive testing is impossible, so one can never prove that all defects were identified
d) Is not correct. To make an assessment whether a defect will cause a failure or not, one must detect the defect first. Saying that no remaining defect will cause a failure implicitly means that all defects were found. This again contradicts principle #2

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

There is at least one test for each column in the decision table. However, column one requires two tests, one where the account is invalid and another where the account is valid, but the password is invalid, so the minimum number of tests is four.

Thus:
a) Is not correct
b) Is not correct
c) Is 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. Exploratory testing is not suitable to speed up tests, which are already specified. It is most useful when there are few or inappropriate specified requirements or significant time pressure on testing
b) Is not correct. The absence of a test charter, which may have been derived from the test analysis, is a poor precondition for the use of exploratory testing
c) Is correct. Exploratory tests should be performed by experienced testers with knowledge of similar applications and technologies
d) Is not correct. Explorative testing alone is not suitable to provide evidence that the test was very intensive, instead the evidence is provided in combination with other test methods

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

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 not correct. It is possible to perform any of the test types (functional, non-functional, white-box) at any test level - so, although it is correct that functional and non-functional testing can be performed at system and acceptance test levels, it is incorrect to state that white-box testing is restricted to component and integration testing
b) Is not correct. It is possible to perform any of the test types (functional, non-functional, white-box) at any test level - so, it is incorrect to state that white-box testing is restricted to component testing
c) Is correct. It is possible to perform any of the test types (functional, non-functional, white-box) at any test level
d) Is not correct. It is possible to perform any of the test types (functional, non-functional, white-box) at any test level - so, it is incorrect to state that white-box testing is restricted to component testing and integration testing

Explanation / Rationale

a) Is correct. Percentage of test cases prepared is a common metric during test preparation while percentage of test cases passed, failed, not run, etc., are common during test execution
b) Is not correct. Defect reports are typically filed during test execution, based on failures found
c) Is not correct. Test environment preparation is part implementation and would generally be complete before test execution
d) Is not correct. Defects are typically reported during test execution, based on failures found, so the cost to find the next defect is available during test execution only

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. 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. 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 correct
b) Is not correct. The evaluation of the test automation skills and training, mentoring and coaching needs of the testers who will use the tool should have been performed as part of the tool selection activity
c) Is not correct. The decision on whether the tool provides the required functionality and does not duplicate existing tools should have been performed as part of the tool selection activity
d) Is not correct. The evaluation of the tool vendor in terms of the training and other support they provide should have been performed as part of the tool selection activity

Explanation / Rationale

a) Is not correct. Risk is determined by considering a combination of the likelihood of problem situations and the harm that may result from them but cannot be calculated by adding these together (the probability would be in the range 0 to 1 and the harm could be in dollars)
b) Is not correct. Risk is determined by considering a combination of a likelihood and an impact. This definition only considers likelihood and chance (both forms of probability) with no consideration of the impact (or harm)
c) Is correct. See reasons from incorrect answers
d) Is not correct. Risk is determined by considering a combination of a likelihood and an impact. This definition only considers hazards and losses (a hazard is a bad event, like a risk, while loss is a form of impact) with no consideration of the likelihood (or probability)

Explanation / Rationale

Traceability assists with:

• Selecting regression tests in terms of analyzing the impact of changes (1D)
• Evaluating completeness of test execution which makes testing auditable (2B)
• Identifying which user stories have open defect reports which improves understandability of test status reports to include status of test basis items (3A)
• Evaluating whether the number of tests for each requirement is consistent with the level of product risk which provides information to assess test process quality (i.e., alignment of test effort with risk) (4C)

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

Explanation / Rationale

a) Is correct. Making decisions about what to test are documented in the test plan. This means when you are planning the test and there are budget limitations, prioritizing is needed; what should be tested and what should be omitted
b) Is not correct. Test monitoring and control
c) Is not correct. Common test metrics
d) Is not correct. It is a part of test analysis

Explanation / Rationale

a) Is not correct. This is the Glossary definition of condition coverage
b) Is not correct. Decision coverage is a higher level of coverage and the two terms are not defined as synonyms in the Glossary
c) Is not correct. This is the Glossary definition of statement coverage
d) Is correct. This is the Glossary definition of coverage as applied to decisions

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

The following partitions can be identified:

1. <= 50, boundary value 50
2. 51 – 55 boundary values 51, 55
3. 56 – 60 boundary values 56, 60
4. >=61 boundary value 61

Boundary value according to glossary V.3.2: A minimum or maximum value of an ordered equivalence partition.

Thus:
a) Is not correct. Does not include all necessary boundary values, but it includes additional values: 0, 49, and 59, which are not boundary values in this equivalence partition
b) Is not correct. Does not include all necessary boundary values. 51 and 55 are missing
c) Is not correct. Does not include necessary boundary values but it includes additional values: 49, 62, and 54, which are not boundary values in this equivalence partition
d) Is correct. includes all necessary boundary values

Explanation / Rationale

a) Is not correct. R4 is dependent on R2, so R2 should be tested before R4
b) Is not correct. R4 is dependent on R2, R5 and R6, so R5 and R6 should be tested before R4
c) Is correct. The tests are specified in a sequence that takes the dependencies into account
d) Is not correct. R2 is dependent on R3, so R3 should be tested before R2

Explanation / Rationale

Performance testing is a test type, not a test level. Component testing focuses on defects in separately testable modules or objects, integration testing on defects in interfaces and interactions, system testing on defects in the whole test object, and acceptance testing is not typically focused on identifying defects.

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

Explanation / Rationale

Considering the potential inconsistencies:

• 6-10 – If librarians should get system responses within 5 seconds, it is NOT inconsistent for borrowers to get system responses within 3 seconds.
• 6-15 - If librarians should get system responses within 5 seconds, it is inconsistent for all users to get system responses within 3 seconds.
• 7-12 – If borrowers can borrow a maximum of 3 books at one time it is NOT inconsistent for them to also reserve books (if they are on-loan).
• 9-11 – If a borrower can be fined for failing to return a book within 3 weeks it is inconsistent for them to also be allowed to borrow a book at no cost for a maximum of 4 weeks – as the length of valid loans are different.

Of the potential inconsistencies, 6-15 and 9-11 are valid inconsistencies.

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

Explanation / Rationale

The following valid input equivalence partitions can be identified:

• Hours

1. Below 3 hours
2. 3 to 6 hours
3. Above 6 hours

• Intensity

4. Very low
5. Low
6. Medium
7. High

The given test cases cover the following valid input equivalence partitions:

Thus, the missing valid input equivalence partitions are: (2), (5) and (7). These can be covered by two test cases, as (2) can be combined with either (5) or (7).
Thus:
a) Is not correct
b) Is correct
c) Is not correct
d) Is not correct

Explanation / Rationale

a) Is correct. This is maintainability testing, not maintenance testing
b) Is not correct. This is a trigger for maintenance testing: Operational tests of the new environment as well as of the changed software
c) Is not correct. This is the trigger for maintenance testing: testing restore/retrieve procedures after archiving for long retention periods
d) Is not correct. This is the trigger for maintenance testing: Reactive modification of a delivered software product to correct emergency defects that have caused actual failures

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 correct. Defects found early are often much cheaper to remove than defects detected later in the lifecycle
b) Is not correct. Dynamic testing still has its challenging because they find other types of defects
c) Is not correct. This is dynamic testing
d) Is not correct. Static testing is important for safety-critical computer systems

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. 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

Considering each of the pieces of information:

1. Degree of impact (severity) of the defect – the developers are already aware of the problem and are waiting to fix it, so this is a less important piece of information.
2. Identification of the test object – as the developers are already aware of the problem and you are performing system testing, and you have already provided the version of the system you are testing you can assume they know the object that was being tested, so this is a less important piece of information.
3. Details of the test environment – the set-up of the test environment may have a noticeable effect on the test results, and detailed information should be provided, so this is an important piece of information.
4. Urgency/priority to fix – the developers are already aware of the problem and are waiting to fix it, so this is a less important piece of information.
5. Actual results – the actual results may well help the developers to determine what is going wrong with the system, so this is an important piece of information.
6. Reference to test case specification – this will show the developers the tests you ran, including the test inputs that caused the system to fail (and expected results), so this is an important piece of information.

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

Explanation / Rationale

a) Is not correct. While impact analysis is useful during maintenance testing it is not necessary for confirmation testing since confirmation testing is on the intended effects of a bug fix or other change
b) Is not correct. Confirmation and regression testing are two separate activities, and confirmation testing is not part of system design
c) Is correct. Impact analysis can be used to select regression tests for maintenance testing
d) Is not correct. Confirmation testing is not part of impact analysis, though confirmation testing will typically happen during maintenance testing

Explanation / Rationale

There are three equivalence partitions:

• No sale completed (0.0 gallons)
• A valid sale occurs (0.1 to 50.0 gallons)
• An invalid amount is selected (50.1 or more gallons)

Thus:
a) Is correct. This set of input values has exactly one test per equivalence partition
b) Is not correct. This set of input values has does not cover the invalid amount partition
c) Is not correct. This set of input values has two tests for the valid sale equivalence partition, which is not the minimum
d) Is not correct. This set of input values covers the three-point boundary values for the two boundaries, not the minimum number required to cover the equivalence partitions

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. Regression testing does not check successful implementation of corrections and confirmation testing does not check for side effects
b) Is not correct. The statement about confirmation testing should be about regression testing
c) Is correct. See reasons from incorrect answers
d) Is not correct. Testing new functionality is not regression testing

Explanation / Rationale

a) Is not correct. Informal review does not use a formal process
b) Is not correct. Use of checklists are optional
c) Is correct. Inspection is a formal process based on rules and checklists
d) Is not correct. Does not explicitly require a formal process and the use of checklists is optional

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

Considering the scenario:

1. ‘testing is based on interface specifications’ – the test basis for integration testing includes interface specifications (along with communication protocol specification), while these are not included for any of the other test levels
2. ‘testing is focused on finding failures in communication’ - failures in the communication between tested components is included as a typical failure for integration testing, but failures in communication is not included for any of the other test levels
3. ‘the test approach uses both functional and structural test types’ - functional and structural test types are both included as possible approaches for integration testing, and would also be appropriate for any of the other test levels, although they are only otherwise explicitly mentioned in the syllabus for system testing

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

Explanation / Rationale

Given the annotated state model below:

The options achieve the following transition coverage:
a) Is not correct: OFF (2) WAIT (1) OFF (2) WAIT (3) TRICKLE (5) CHARGE (9) HIGH (10) CHARGE (7) LOW = 7 transitions (out of 10)
b) Is not correct: WAIT (3) TRICKLE (4) WAIT (1) OFF (2) WAIT (3) TRICKLE (5) CHARGE (7) LOW (8) CHARGE = 7 transitions (out of 10)
c) Is not correct: HIGH (10) CHARGE (7) LOW (8) CHARGE (6) TRICKLE (4) WAIT (3) TRICKLE (4) WAIT (3) TRICKLE = 6 transitions (out of 10)
d) Is correct: WAIT (3) TRICKLE (5) CHARGE (9) HIGH (10) CHARGE (6) TRICKLE (4) WAIT (1) OFF (2) WAIT = 8 transitions (out of 10)

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