Explanation / Rationale

a) Is not correct. The two methods are used sequentially, not simultaneously
b) Is correct. The primary sources of information come from the experienced testers, who are the experts. The consultant’s industry averages augment the original estimate from published metrics
c) Is not correct. The expert-based approach is the primary approach, augmented by a metrics-based approach
d) Is not correct. We do not know if this project is following Agile methods, and burndown charts do not come from external consultants

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

a) Is not correct. This is a white-box test technique
b) Is not correct. This is a white-box test technique
c) Is not correct. This is an experience-based test technique
d) Is correct. Black-box test techniques are based on an analysis of the appropriate test basis (e.g., formal requirements documents, specifications, use cases, user stories)

Explanation / Rationale

a) Is not correct. Based on definition of equivalence partition
b) Is correct. Based on definition from Glossary
c) Is not correct. Based on Glossary definition of testware
d) Is not correct. Based on definition of test oracle

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

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 correct. Exploratory testing is a form of experience-based testing, which benefits from the skills and experience of the tester
b) b) Is not correct. Exploratory testing is useful to complement formal testing techniques
c) Is not correct. In session-based test management, exploratory testing is conducted within a defined time-box, and the tester uses a test charter containing test objectives to guide the testing
d) Is not correct. Exploratory testing can incorporate the use of other black-box, white-box, and experience-based techniques referenced in this syllabus

Explanation / Rationale

a) Is not correct. Analyzing a defect is part of debugging, not testing
b) Is correct. Creating test data is a test implementation task
c) Is not correct. While a tester may need to identify a test item’s version for results reporting purposes, assigning a test item’s version is part of configuration management
d) Is not correct. Writing a user story is not a testing activity and should be done by the product owner

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

a) Is not correct. It is described that the software architect must have completed the system specification
b) Is not correct. ‘Checklist-based’, last sentence it is documented that you should also look for defects outside the checklist
c) Is not correct. It is described: every reviewer did his review done comment
d) Is correct. It is described that a checklist is available, but who provides the checklist?

Explanation / Rationale

This question is looking for bad application of product risk analysis.

a) Is not correct. As we are told security flaws have a particularly high impact, their risk level will be higher, and thus we have prioritized the security testing ahead of some other testing. Thus, product risk analysis has influenced the testing properly.
b) Is correct. As less defects than expected have been found in the network module, the perceived risk in this area should be lower, and so less testing should be focused on this area, NOT additional testing. Thus, product risk analysis has NOT CORRECTLY influenced the testing in this situation
c) Is not correct. Because the users had problems with the user interface of the previous system, there is now high awareness of the risk associated with the user interface, which has resulted in additional usability testing being planned. Thus, product risk analysis has properly influenced the thoroughness and scope of testing
d) Is not correct. As the time needed to load web pages has been identified as crucial to the success of the new website, the performance of the website should be considered a risk, and the employment of an expert in performance testing helps to mitigate this risk. Thus, product risk analysis has properly influenced the testing

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

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

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

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

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. Requirement management tools are not particularly suitable for developers
b) Is not correct. Configuration management tools are not particularly suitable for developers
c) Is correct. Static analysis tools are especially suitable for developers
d) Is not correct. Performance testing tools are not better suited for developers than for testers

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

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

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. 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. This is an objective for a pilot, but you have achieved it because you understand the tool much better due to the pilot
b) Is not correct. This is an objective for a pilot, but you have achieved it because you have tailoring your testing processes
c) Is not correct. This is an objective for a pilot, but you have achieved it because you have standardized an approach to using the tool and its associated work products
d) Is correct. Assessing the benefits and configuring the metrics collection are the two objectives missing from this list

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

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

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

a) Is not correct. While this test does match the description of an integration test, it is a non-functional test
b) Is correct. This test matches the description of an integration test and it is a non-functional test
c) Is not correct. This test does not match the description of a component test and it is not a functional test
d) Is not correct. While this test is a non-functional test, it does not match the description of a component test

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. 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 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 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. This information has been defined earlier in the test project
b) Is not correct. This information is included in a test report: information on what occurred during a test period
c) Is not correct. This information is included in a test report:

• Status of testing and product quality with respect to the exit criteria or definition of done
• Metrics of defects, test cases, test coverage, activity progress, and resource consumption

d) Is not correct. This information is included in a test report: Information and metrics to support recommendations and decisions about future actions, such as an assessment of defects remaining, the economic benefit of continued testing, outstanding risks, and the level of confidence in the tested software

Explanation / Rationale

Product risks exist when a work product may fail to satisfy legitimate needs, while project risks are situations that could have a negative impact on the project’s ability to achieve its objectives. So:

A. Incorrect totals on screens = product risk
B. Change to acceptance criteria during acceptance testing = project risk
C. Users find the soft keyboard too hard to use with your app = product risk
D. System responds too slowly to user input during search string entry = product risk
E. Testers not allowed to report test results in daily standup meetings = project risk

Thus:
a) Is not correct. This list is entirely backwards
b) Is correct
c) Is not correct. While E is about product quality and product risks, the failure to communicate test results is a project risk per the syllabus
d) Is not correct. Product risks can be functional and non-functional, so d is also a product risk