A test task that usually occurs during test implementation is to make sure the planned test
environment is ready to be delivered. The test environment is the hardware and software
configuration on which the tests are executed, and it should be as close as possible to the production
environment where the software system will operate. The test environment should be planned,
prepared, and verified before the test execution, to ensure that the test conditions, the test data, the
test tools, and the test interfaces are available and functional. The other options are not test tasks
that usually occur during test implementation, but rather test tasks that occur during other test
activities, such as:
Find, analyze, and remove the causes of the failures highlighted by the tests: This is a test task that
usually occurs during test analysis and design, which is the activity of analyzing the test basis,
designing the test cases, and identifying the test data. During this activity, the testers can use
techniques such as root cause analysis, defect prevention, or defect analysis, to find, analyze, and
remove the causes of the failures highlighted by the previous tests, and to prevent or reduce the
occurrence of similar failures in the future tests.
Archive the testware for use in future test projects: This is a test task that usually occurs during test
closure, which is the activity of finalizing and reporting the test results, evaluating the test process,
and identifying the test improvement actions. During this activity, the testers can archive the
testware, which are the test artifacts produced during the testing process, such as the test plan, the
test cases, the test data, the test results, the defect reports, etc., for use in future test projects, such
as regression testing, maintenance testing, or reuse testing.
Gather the metrics that are used to guide the test project: This is a test task that usually occurs
during test monitoring and control, which is the activity of tracking and reviewing the test progress,
status, and quality, and taking corrective actions when necessary. During this activity, the testers can
gather the metrics, which are the measurements of the testing process, such as the test coverage,
the defect density, the test effort, the test duration, etc., that are used to guide the test project, such
as planning, estimating, scheduling, reporting, or improving the testing process. Reference: ISTQB
Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.1, Test Planning1
ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.2, Test Monitoring and Control1
ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.3, Test Analysis and Design1
ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.4, Test Implementation1
ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.5, Test Execution1
ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.6, Test Closure1
ISTQB® Glossary of Testing Terms v4.0, Test Environment, Test Condition, Test Data, Test Tool, Test
Interface, Failure, Root Cause Analysis, Defect Prevention, Defect Analysis, Testware, Regression
Testing, Maintenance Testing, Reuse Testing, Test Coverage, Defect Density, Test Effort, Test
Duration2
