QB3

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.

a) Correct answer. This is an objective listed in section 1.1.

b) Is not correct: this is debugging per section 1.1.2.

c) Is not correct: this is an activity within the test execution group of activities within the test process described in section 1.4.2.

d) Is not correct: this is part of debugging per section 1.1.2.

a) Is not correct: the root cause is the distraction that the programmer experienced while programming

b) Is not correct: the accepting of invalid inputs is the failure.

c) Is not correct: the error is the mistaken thinking that resulted in putting the defect in the code.

d) Is correct: the problem in the code is a defect.

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. 

a) Is not correct: the programmer appears to be performing unit testing on their own.

b) Is not correct: code coverage is useful for unit testing, but it is not a tester mindset described in section 1.5.2

c) Is not correct: per section 1.5.2, the programmer’s mindset included contemplating what might be wrong with the code, but that is not a tester’s mindset

d) Is correct: this tester mindset in section 1.5.2, attention to detail, will help programmers find defects during unit testing

Traceability assists with:

• Selecting regression tests in terms of analyzing the impact of changes.

• Evaluating completeness of test execution which makes testing auditable.

• Identifying which user stories have open defect reports which improves understandability of test status reports to include status of test basis items.

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

Therefore, d is correct, per section 1.4.4

a) Is not correct: while enabling required tests to be identified in an early stage is a testing contribution to success per section 1.2.1, there is no indication in the question that the tester did so.

b) Is not correct: ensuring processes are carried out properly is part of quality assurance, not a testing contribution to success, per sections 1.2.1 and 1.2.2

c) Is correct: reducing the risk of fundamental design defects is a testing contribution to success per section 1.2.1. Database structure is related to design, and performance problems can be a significant product risk.

d) Is not correct: while reducing the risk of untestable functionality is a testing contribution to success per section 1.2.1, the tester here has not identified something untestable, but rather something that would result in performance tests failing

a) Is not correct: analyzing a defect is part of debugging, not testing, per section 1.1.2

b) Is correct: creating test data is a test implementation task per section 1.4.2.

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, per section 5.4

d) Is not correct: writing a user story is not a testing activity and should be done by the product owner