1.4.2 Test Activities and Tasks Flashcards
A test process consists of the following main groups of activities:
- Test planning
- Test monitoring and control
- Test analysis
- Test design
- Test implementation
- Test execution
- Test completion
Each constituent activity test process consists of multiple individual tasks, which would vary
from one project or release to another.
many of these test process activity groups may appear logically sequential, they are often implemented
iteratively
many of these main activity groups are tailored
within the context of the system and the project
Test planning involves activities that define
the objectives of testing and the approach for meeting test objectives within constraints imposed by the context
examples of constraints imposed by the testing context:
specifying suitable test techniques and tasks, formulating a test schedule for meeting a deadline
Test plans may be revisited based on
feedback from monitoring and control activities.
Test monitoring involves
the ongoing comparison of actual progress against planned progress using any test monitoring metrics defined in the test plan.
Test control involves
taking actions necessary to meet the objectives of the test plan (which may be updated over time).
Test monitoring and control are supported by
the evaluation of exit criteria
referred to as the definition of done in some software development lifecycle models
Test monitoring and control
evaluation of exit criteria for test execution as part of a given test level may include:
Checking test results and logs against specified coverage criteria
Assessing the level of component or system quality based on test results and logs
Determining if more tests are needed
example when more tests are needed
if tests originally intended to achieve a certain level of product risk coverage failed to do so, requiring additional tests to be written and executed
Test progress against the plan is communicated to stakeholders in test progress reports, including
deviations from the plan and information to support any decision to stop testing.
Test progress against the plan is communicated to stakeholders in
test progress reports
test progress reports includes
deviations from the plan and information to support any decision to stop testing
During test analysis, the test basis is analyzed to
identify testable features and define associated test conditions.
test analysis determines
“what to test” in terms of measurable coverage criteria.
Test analysis includes the following major activities:
Analyzing the test basis appropriate to the test level being considered
Evaluating the test basis and test items to identify defects of various types
Identifying features and sets of features to be tested
Defining and prioritizing test conditions for each feature
Capturing bi-directional traceability between each element of the test basis and the associated test conditions
Defining and prioritizing test conditions for each feature based on:
analysis of the test basis, considering functional, non-functional, and structural characteristics, other business and technical factors levels of risks
Analyzing the test basis appropriate to the test level being considered
Requirement specifications
Design and implementation information
The implementation of the component or system itself
Risk analysis reports
Requirement specifications, such as
business requirements,
functional requirements,
system requirements,
user stories,
epics,
use cases
Requirement specification that specify
desired functional and non-functional component or system behavior
Design and implementation information, that
specify component or system structure
Design and implementation information, such as
system or software architecture diagrams or documents,
design specifications,
call flow graphs,
modelling diagrams
interface specifications