To Memorize

Question 1

test progress reports

Answer 1

Test period

Test progress (e.g., ahead or behind schedule), including any notable deviations

Impediments (blocks) for testing, and their workarounds

Test metrics (see section 5.3.1 for examples)

New and changed risks within testing period

Testing planned for the next period

Question 2

test completion

Answer 2

Test summary

Testing and product quality evaluation based on the original test plan (i.e., test objectives and exit criteria)
Deviations from the test plan (e.g., differences from the planned schedule, duration, and effort).

Testing impediments and workarounds

Test metrics based on test progress reports

Unmitigated (mitigate: make less severe) risks, defects not fixed

Lessons learned that are relevant to the testing

Question 3

For every software development activity,

Answer 3

there is a corresponding test activity, so that all development activities are subject to quality control

Question 4

Different test levels (see chapter 2.2.1) have

Answer 4

specific and different test objectives, which allows for testing to be appropriately comprehensive while avoiding redundancy

Question 5

Test analysis and design for a given test level begins

Answer 5

during the corresponding development phase of the SDLC, so that testing can adhere to the principle of early testing (see section 1.3)

Question 6

Testers are involved in reviewing work products as soon as

Answer 6

drafts of this documentation are available, so that this earlier testing and defect detection can support the shift-left strategy (see section 2.1.5)

Question 7

Testers involved in release planning participate in

Answer 7

writing testable user stories and acceptance criteria (see section 4.5),

participate in project and quality risk analyses (see section 5.2),

estimate test effort associated with user stories (see section 5.1.4),

determine the test approach,

and plan the testing for the release.

Question 8

Testers involved in iteration planning:

Answer 8

participate in the detailed risk analysis of user stories,

determine the testability of user stories,

break down user stories into tasks (particularly testing tasks),

estimate test effort for all testing tasks,

identify and refine functional and non-functional aspects of the test object.

Question 9

Context of testing

Answer 9

scope, test objectives, constraints, test basis

Question 10

Increased test effectiveness / efficiency

Answer 10

(e.g., by implementing suggestions for process improvement)


Question 11

Increased quality of testware

Answer 11

(e.g., by jointly reviewing the test processes)


Question 12

Team bonding and learning

Answer 12

(e.g., as a result of the opportunity to raise issues and propose improvement points)


Question 13

Improved quality of the test basis

Answer 13

(e.g., as deficiencies in the extent and quality of the requirements could be addressed and solved)


Question 14

Better cooperation between development and testing

Answer 14

(e.g., as collaboration is reviewed and optimized regularly)

Question 15

Management tools – increase the test process efficiency

Answer 15

by facilitating management of the SDLC, requirements, tests, defects, configuration (Jira, confluence)