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. ‘Beware of the pesticide paradox’ is concerned with re-running the same tests and their fault-finding effectiveness decreasing
b) Is not correct. This testing principle is concerned with performing testing differently based on the context (e.g., games vs safety-critical)
c) Is not correct. This testing principle is concerned with the difference between a tested and fixed system and a validated system. No ‘errors’ does not mean the system is fit for use
d) Is correct. If clusters of defects are identified (areas of the system containing more defects than average), then testing effort should be focused on these areas

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

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

The following valid input equivalence partitions can be identified:

• Hours

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

• Intensity

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

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

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

Explanation / Rationale

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

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

Explanation / Rationale

a) Is not correct. Technical reviews are appropriate for technical documents such as a system architecture
b) Is correct. Adequate time for preparation is important, but people are working overtime and no adjustments are made for this new set of tasks
c) Is not correct. Gathering metrics from a review to evaluate participants is a factor that leads to failure, not success, because it destroys trust
d) Is not correct. A well-managed review meeting is important, but there is no reason to think the review meeting will not be well managed based on the information provided

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

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

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

Explanation / Rationale

The complete decision table is shown below:

To achieve full coverage, test cases covering rules 2 and 3 are needed. DT4 satisfies the constraints of rule 2, while DT2 satisfies the constraints of rule 3.

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

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

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

Explanation / Rationale

a) Is not correct. Testing does not identify the source of defects, debugging identifies the source of defects
b) Is correct. Dynamic testing can show failures that are caused by defects in the software. Debugging eliminates the defects, which are the source of failures
c) Is not correct. Testing does not remove faults, but debugging removes faults, which is synonyms for defects, that may cause the failures
d) Is not correct. Dynamic testing does not directly prevent the causes of failures (defects) but detects the presence of defects

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

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

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

Thus:
a) Is not correct. Only two of the equivalence partitions are covered in this set of tests
b) Is not correct. Each of those four boundary values are included in this set of tests, but the question asked for equivalence partition coverage with minimal tests, so either 0.5 or 25.0 should be dropped
c) Is correct. Each of these three equivalence partitions are covered in this set of tests
d) Is not correct. Only one of those equivalence partitions is covered by this test

Explanation / Rationale

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

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

Explanation / Rationale

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

a) Is not correct. Static testing (reviews) contributes, but could not ensure, that requirements are detailed enough
b) Is correct. Testing contributes to the achievement of quality in a variety of ways, e.g., such as reducing the risk of inadequate software quality
c) Is not correct. This is quality assurance but not testing
d) Is not correct. The quality cannot be measured by counting the number of executed test cases without knowing the outcome

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

Explanation / Rationale

a) Is not correct. Statement testing exercises the executable statements in the code, which might result in the absence of certain greetings not being tested
b) Is not correct. Unless the test charter specifically mentioned testing both the presence and the absence of each type of greeting, coverage can be difficult to assess for an exploratory test
c) Is not correct. State transition testing is useful for situations where the test object responds differently to an input depending on current conditions or previous history, but in this case the test object must decide whether the current date matches a particular milestone and thus whether to display the relevant greeting
d) Is correct. Decision testing involves test cases that follow the control flows that occur from a decision point, which in this case would be deciding whether a greeting should or should not be given

Explanation / Rationale

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

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

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)