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

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

Considering each statement:

1. Each development activity should have a corresponding testing activity. TRUE
2. Reviewing should start as soon as final versions of documents become available. FALSE – it should start as soon as drafts are available
3. The design and implementation of tests should start during the corresponding development activity. FALSE – the analysis and design of tests should start during the corresponding development activity, not the implementation
4. Testing activities should start in the early stages of the software development lifecycle. TRUE

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

Explanation / Rationale

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

Explanation / Rationale

a) Is not correct. This is an example of a mistake made by the developer
b) Is not correct. This is an example of a defect (something wrong in the code that may cause a failure)
c) Is correct. This is a deviation from the expected functionality - a cruise control system should not be affected by the radio
d) Is not correct. This is an example of a defect (something wrong in a specification that may cause a failure if subsequently implemented)

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

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

a) Is correct. One of the typical tasks of a test manager
b) Is not correct. One of the typical tasks of a tester
c) Is not correct. One of the typical tasks of a tester
d) Is not correct. One of the typical tasks of a tester

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

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

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

Explanation / Rationale

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

Explanation / Rationale

a) Is not correct. The 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. 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. 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

The correct pairing of descriptions with the different categories of test techniques is:

• Black-box test techniques
Deviations from the requirements are checked (4) User stories are used as the test basis (5)
• White-box test techniques
Coverage is measured based on a selected structure of the test object (1) The processing within the test object is checked (2)
• Experience-based test techniques
Tests are based on defects’ likelihood and their distribution (3)

Thus:
a) Is correct
b) Is not correct
c) Is not 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 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

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

Explanation / Rationale

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

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

Thus:
a) Is not correct. 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. This is an objective listed
b) Is not correct. This is debugging
c) Is not correct. This is an activity within the test execution group of activities within the test process
d) Is not correct. This is part of debugging

Explanation / Rationale

a) Is not correct. 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. 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

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

Explanation / Rationale

a) Is not correct. While 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 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

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

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

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

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

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