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

a) Is correct. Test case execution (e.g., number of test cases run/not run, and test cases passed/failed)
b) Is not correct. This metric can be measured, but its value is low. The number of testers does not give any information about the quality of the test object or test progress
c) Is not correct. the coverage of requirements by source code is not measured during test execution. At most, the TEST(!) coverage of the code or requirements is measured
d) Is not correct. This metric is part of test preparation and not test execution

Explanation / Rationale

a) Is not correct. Defect clustering has to do with where defects are most likely to be found, not whether all of them can be found
b) Is correct. Testing can show the presence of defects but cannot prove their absence, which makes it impossible to know if you have caught all the bugs. Further, the impossibility of exhaustive testing makes it impossible for you to catch all the bugs
c) Is not correct. This principle says that you can find and remove many bugs but still release an unsuccessful software product, which is not what the product owner is asking you to ensure
d) Is not correct. Root cause analysis is not a testing principle

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

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

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. Definition of feature according to glossary
b) Is correct. From glossary
c) Is not correct. Definition of functionality suitability according to glossary
d) Is not correct. Like Definition of Decision table testing according to glossary

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 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 not correct. error guessing is not a usability technique for guessing how users may fail to interact with the test object
b) Is not correct. Although a tester who used to be a developer may use their personal experience to help them when performing error guessing, the technique is not based on prior knowledge of development
c) Is correct. The basic concept behind error guessing is that the tester tries to guess what mistakes may have been made by the developer and what defects may be in the test object based on past-experience (and sometimes checklists)
d) Is not correct. Duplicating the development task has several flaws that make it impractical, such as the requirement for the tester to have equivalent skills to the developer and the time involved in performing the development. It is not error guessing

Explanation / Rationale

a) Is not correct. Relevant for integration testing
b) Is not correct. Relevant for component testing
c) Is correct. For acceptance testing, tests are designed to cover all workflows defined in the functional requirements documents.
d) Is not correct. Relevant for system testing

Explanation / Rationale

For the input equivalence partitions given, the above used boundary value technique yields the following 8 coverage items:

10°C, 11°C, 15°C, 16°C, 19°C, 20°C, 22°C, 23°C.

Hence, the options have the following boundary value coverage:
a) Is not correct. 4 out of 8 (11, 20 ,22 and 23)
b) Is not correct. 3 out of 8 (15, 19 and 23)
c) Is correct. 5 out of 8 (10, 16, 19, 22 and 23)
d) Is not correct. 3 out of 8 (15, 19 and 22)

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

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 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 correct. The metrics-based approach: estimating the testing effort based on metrics of former similar projects or based on typical values
b) Is not correct. This is expert-based approach: estimating the tasks based on estimates made by the owners of the tasks or by experts
c) Is not correct. This is expert-based approach: estimating the tasks based on estimates made by the responsible team of the tasks or by experts
d) Is not correct. This is expert-based approach: estimating the tasks based on estimates made by the owners of the tasks or by experts

Explanation / Rationale

a) Is not correct. The test described is a non-functional test, it is a portability test, not a performance test
b) Is not correct. Processor test is not a defined test type
c) Is not correct. The test described is a non-functional test, specifically a portability test
d) Is correct. Testing supported devices is a non-functional test, specifically a portability test

Explanation / Rationale

a) Is correct. The management decides about performing the review
b) Is not correct. The moderator, not the review leader should ensure the effective running of review meetings
c) Is not correct. The author fixes the work product under review
d) Is not correct. The manager monitors ongoing cost-effectiveness

Explanation / Rationale

a) Is correct. Incremental development involves establishing requirements, designing, building, and testing a system in pieces
b) Is not correct. This is a sequential model
c) Is not correct. This describes the waterfall model
d) Is not correct. Testing alone is not an increment/additional step in the development

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

a) Is not correct. Statement coverage measures the percentage of statements exercised by test cases
b) Is correct. Statement testing exercises the executable statements in the code. Statement coverage is measured as the number of statements executed by the tests divided by the total number of executable statements in the test object, normally expressed as a percentage
c) Is not correct. The coverage does not measure pass/fail
d) Is not correct. It is a metric and does not provide true/false statements

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

a) Is not correct. Estimates may be updated as more information becomes available, but estimates are needed to assist with planning before the testing starts
b) Is not correct. In the expert-based approach, the experts need to be experts in testing, not in using the test object
c) Is correct. Test Managers, who will be leading testers doing the testing, are considered experts in their respective areas and suitable for estimating the necessary resources needed
d) Is not correct. While it is useful to know the testing costs from previous projects, a more sophisticated approach is needed than simply taking an average of past projects (the new project may not be like the previous projects, e.g., it may be far larger or far smaller than previous projects)

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

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

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

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

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. While deviation from standards is a typical, we are not given any standard with which the user stories should comply
b) Is correct. Contradiction is a typical requirements defect. AC3 and AC5 conflict if the Rod is touched to an object that extends more than 1 meter in any direction from the point at which touched, since AC1 does not limit the size of the objects to be touched
c) Is not correct. While security vulnerabilities are typical defects, there is nothing here related to security
d) Is not correct. While test coverage gaps are typical defects, including missing tests for acceptance criteria, we are not provided with any information about which tests do and do not exist

Explanation / Rationale

a) Is not correct. The lack of familiarity of the requirements author with the fitness domain is a root cause
b) Is not correct. The lack of training of the tester in state transition testing was one of the root causes of the defect (the developer presumably created the defect, as well)
c) Is correct. The incorrect configuration data represents faulty software in the fitness tracker (a defect), that may cause failures
d) Is not correct. The lack of experience in designing user interfaces for wearable devices is a typical example of a root cause of a defect

Explanation / Rationale

a) Is correct. For a loop construct, statement coverage only requires that all statements within the loop are executed, but decision coverage requires testing of both the conditions where the loop is executed and when it is bypassed
b) Is not correct. For a loop construct, statement coverage only requires that all statements within the loop are executed, but decision coverage requires testing of both the conditions where the loop is executed and when it is bypassed
c) Is not correct. Checklists are based on experience, defect and failure data, knowledge about what is important for the user, and an understanding of why and how software fails, none of which is likely to have led to the inclusion of such a test condition
d) Is not correct. While it is possible that someone might anticipate a developer making the mistaken assumption that there would always be at least one transaction in a month for every account, only decision testing guarantees testing of that condition

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

a) Is not correct. Reviews should increase the quality of specifications, however the time required for development and testing should decrease
b) Is not correct. Detecting defects is generally easier earlier in the lifecycle
c) Is not correct. Reviews will result in fewer missed requirements and better communication between testers and developers, however this is not true for static analysis
d) Is correct. This is a benefit of static analysis

Explanation / Rationale

a) Is not correct. The test result is given in the short summary
b) Is correct. When testing different versions of software, identifying information is necessary
c) Is not correct. You are just writing the defect report; hence, the status is automatically open
d) Is not correct. This information is useful for the tester but does not need to be included in the defect report

Explanation / Rationale

a) Is correct. See reasons from incorrect answers
b) Is not correct. The “degree of tester’s independence” does not play a role in exit criteria
c) Is not correct. “Availability of test environment” is an entry criterion
d) Is not correct. “The Qualification of Tester” is not a typical exit criterion