1.4.3 TEST WORK PRODUCTS

Question 1

Test work products are created as part of

Answer 1

the test process.

Question 2

Just as there is significant variation in the way that organizations implement the test process, there is also significant variation in the

Answer 2

the types of work products created during that process,
the ways those work products are organized and managed, and
the names used for those work products.

Question 3

ISO standard (ISO/IEC/IEEE 29119-3) may also serve as a guideline for

Answer 3

test work products.

Question 4

Many of the test work products described in this section can be captured and managed using

Answer 4

test management tools
defect management tools

Question 5

Test planning work products typically include

Answer 5

one or more test plans.

Question 6

The test plan includes information about

Answer 6

the test basis
exit criteria

Question 7

exit criteria (or definition of done) which will be used during test

Answer 7

monitoring and control.

Question 8

Test monitoring and control work products typically include various types of test reports, including

Answer 8

test progress reports (ongoing and/or a regular basis)
and
test summary reports (at milestones completion).

Question 9

All test reports should provide

Answer 9

up-to-date and audience-relevant details about the test progress
a summary of the test execution results

Question 10

Test monitoring and control work products should also address project management concerns, such as

Answer 10

task completion,
resource allocation and usage
effort.

Question 11

Test analysis work products include defined and prioritized test conditions, each of which is ideally

Answer 11

bidirectionally traceable to the specific element(s) of the test basis it covers.

Question 12

For exploratory testing, test analysis may involve the creation of

Answer 12

test charters.

Question 13

Test analysis may also result in the discovery and reporting of defects in

Answer 13

the test basis.

Question 14

Test design results in test cases and sets of test cases to exercise

Answer 14

the test conditions defined in test analysis.

Question 15

It is often a good practice to design high-level test cases,

Answer 15

without concrete values for input data and expected results.

Question 16

high-level test cases are reusable across

Answer 16

multiple test cycles with different concrete data,

Question 17

Ideally, each test case is bidirectionally traceable to

Answer 17

the test condition(s) it covers.

Question 18

Test design also results in:

Answer 18

the design and/or identification of the necessary test data
the design of the test environment
the identification of infrastructure and tools

Question 19

the extent to which Test design results are documented

Answer 19

varies significantly.

Question 20

Test implementation work products include:

Answer 20

Test procedures and the sequencing of those test procedures
Test suites
A test execution schedule

Question 21

Ideally, once test implementation is complete, achievement of coverage criteria established in the test plan can be demonstrated via bi-directional traceability

Answer 21

between test procedures and specific elements of the test basis,
through the test cases
and test conditions.

Question 22

In some cases, test implementation involves creating work products using or used by tools, such as

Answer 22

service virtualization
automated test scripts.

Question 23

Test implementation also may result in the creation and verification of

Answer 23

test data and the test environment.

Question 24

The completeness of the documentation of the data and/or environment verification results

Answer 24

may vary significantly.

Question 25

The test data serve to assign concrete values to

Answer 25

the inputs of test cases. expected results of test cases.

Question 26

concrete values, together with explicit directions about the use of the concrete values, turn high-level test cases into

Answer 26

executable low-level test cases.

Question 27

The same high-level test case may use different test data when

Answer 27

executed on different releases of the test object.

Question 28

The concrete expected results which are associated with concrete test data are identified by

Answer 28

using a test oracle.

Question 29

In exploratory testing, some test design and implementation work products may be

Answer 29

created during test execution,

Question 30

the extent to which exploratory tests (and their traceability to specific elements of the test basis) are documented

Answer 30

may vary significantly.

Question 31

Test conditions defined in test analysis may be

Answer 31

further refined in test implementation.

Question 32

Test execution work products include:

Answer 32

Documentation of the status of individual test cases or test procedures Defect reports Documentation about which test item(s), test object(s), test tools, and testware were involved in the testing

Question 33

test item(s) involved in the testing

Answer 33

test object(s), test tools, and testware

Question 34

some test cases or test procedures status

Answer 34

ready to run, pass, fail, blocked, deliberately skipped, etc.

Question 35

Ideally, once test execution is complete, the status of each element of the test basis

Answer 35

can be determined and reported via bi-directional traceability with the associated the test procedure(s).

Question 36

For example, once test execution is complete, we can say which requirements have

Answer 36

passed all planned tests, failed tests and/or have defects associated with them planned tests still waiting to be run.

Question 37

determination and reporting the status of each element of the test basis, enables

Answer 37

verification that the coverage criteria have been met the reporting of test results in terms that are understandable to stakeholders.

Question 38

Test completion work products include

Answer 38

test summary reports, action items for improvement of subsequent projects or iterations, change requests or product backlog items finalized testware