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

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

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

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

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. 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. The book provides general guidance, and is not a formal requirements document, a specification, or a set of use cases, user stories, or business processes
b) Is not correct. While you could consider the list as a set of test charters, it more closely resembles the list of test conditions
c) Is correct. The list of user interface best practices is the list of test conditions
d) Is not correct. The tests are not focused on failures that could occur, but rather on knowledge about what is important for the user, in terms of usability

Explanation / Rationale

a) Is not correct. This activity is performed during the test design activity (test design)
b) Is not correct. This activity is performed during the test implementation activity (test implementation)
c) Is not correct. This activity is performed during the test completion activity (test completion)
d) Is correct. This activity is performed during the test analysis activity (test analysis)

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. 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 correct. Impact analysis may be used to identify those areas of the system that will be affected by the fix, and so the extent of the impact (e.g., necessary regression testing) can be used when deciding if the change is worthwhile
b) Is not correct. Although testing migrated data is part of maintenance testing (see conversion testing), impact analysis does not identify how this is done
c) Is not correct. Impact analysis shows which parts of a system are affected by a change, so it can show the difference between different hot fixes in terms of the impact on the system, however it does not give any indication of the value of the changes to the user
d) Is not correct. Impact analysis shows which parts of a system are affected by a change; it cannot provide an indication of the effectiveness of test cases

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 correct. The statement is true. Achieving 100% decision coverage guarantees 100% statement coverage
b) Is not correct. The statement is false because achieving 100 % statement coverage does not in any case mean that the decision coverage is 100%
c) Is not correct. The statement is false because we can only do statements about 100% values
d) Is not correct. The statement is false

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

The correct pairings of test activities and test tools are:

1. Performance measurement and dynamic analysis – (b) Dynamic analysis tools
2. Test execution and logging – (a) Code coverage tools
3. Management of testing and testware – (d) Defect management tools
4. Test design – (c) Test data preparation tools

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

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

a) Is correct. The facilitator or moderator runs the review meetings
b) Is not correct. This is not a role name for a formal review participant
c) Is not correct. The facilitator or moderator runs the review meetings
d) Is not correct. The facilitator or moderator runs the review meetings

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

a) Is not correct. A path through source code is one potential route through the code from the entry point to the exit point that could exercise a range of decision outcomes. Two different paths may exercise all but one of the same decision outcomes, and by just changing a single decision outcome a new path is followed. Test cases that would achieve decision coverage are typically a tiny subset of the test cases that would achieve path coverage. In practice, most non-trivial programs (and all programs with unconstrained loops, such as ‘while’ loops) have a potentially infinite number of possible paths through them and so measuring the percentage covered is practically infeasible
b) Is not correct. Coverage of business flows can be a focus of use case testing, but use cases rarely cover a single component. It may be possible to cover the decisions within business flows, but only if they were specified in enough detail, however this option only suggests coverage of “business flows” as a whole. Even if business flows would cover some decisions, the measure “Decision Coverage” don’t measure the percentage of business flows, but the percentage of decision outcomes exercised by the business flows
c) Is not correct. Achieving full decision coverage does require all ‘if’ statements to be exercised with both true and false outcomes, however, there are typically several other decision points in the code (e.g., ‘case’ statements and the code controlling loops) that also need to be taken into consideration when measuring decision coverage
d) Is correct. Decision coverage is a measure of the proportion of decision outcomes exercised (normally presented as a percentage)

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

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 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. 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 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. 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 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. 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. This is error guessing
b) Is not correct. This is black-box test technique
c) Is correct. See reasons from incorrect answers
d) Is not correct. This is exploratory testing

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

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

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