[L1] Fundamental Test Process

Test Execution

Most visible part of testing

Test Planning & Control : ^ v

Test Analysis and Design

Test Implementation and Execution

Evaluation Exit Criteria and Reporting

Test Closure

Fundamental Test Process:

T:

TAD

TIE

EECR

TC

Test Planning

Determining the scope and risks and identifying the objectives of testing

Test Planning

Defining the overall approach of testing, including the definition of the test levels and entry and exit criteria

Test Planning

Integrating and coordinating the testing activities into the software life cycle activities (acquisition, supply, development, operation and maintenance)

Test Planning

Making decisions about what to test, what roles will perform the test activities, how the test activities should be done, and how the test results will be evaluated

Test Planning

Scheduling test analysis and design activities, test implementation, execution and evaluation

Test Planning

Assigning resources for the different activities defined

Test Planning

Defining the amount, level of detail, structure and templates for the test documentation

Test Planning

Selecting metrics for monitoring and controlling test preparation and execution, defect resolution and risk issues

Control

Making decisions based on information from test monitoring

Control

Re-prioritizing tests when an identified risk occurs (e.g. software delivered late)

Control

Changing the test schedule due to availability or unavailability of a test environment

Control

Setting an entry criterion requiring fixes to have been re-tested (confirmation tested) by a developer before accepting them into a build

Test Analysis and Design

Reviewing the test basis (such as requirements, software integrity level (risk level), risk analysis reports, architecture, design, interface specifications)

Test Analysis and Design

Evaluating testability of the test basis and test objects

Test Analysis and Design

Identifying and prioritizing test conditions based on analysis of test items, the specification, behavior and structure of the software

Test Analysis and Design

Designing and prioritizing high level test cases

Test Analysis and Design

Identifying necessary test data to support the test conditions and test cases

Test Analysis and Design

Designing the test environment setup and identifying any required infrastructure and tools

Test Implementation and Execution

Finalizing, implementing and prioritizing test cases (including the identification of test data)

Test Implementation and Execution

Developing and prioritizing test procedures, creating test data and, optionally, preparing test harnesses and writing automated test scripts

Test Implementation and Execution

Creating test suites from the test procedures for efficient test execution

Test Implementation and Execution

Verifying that the test environment has been set up correctly

Test Implementation and Execution

Verifying and updating bi-directional traceability between the test basis and test cases

Test Implementation and Execution

Executing test procedures either manually or by using test execution tools, according to the planned sequence

Test Implementation and Execution

Logging the outcome of test execution and recording the identities and versions of the software under test, test tools and testware

Test Implementation and Execution

Comparing actual results with expected results

Test Implementation and Execution

Reporting discrepancies as incidents and analyzing them in order to establish their cause

Evaluation Exit Criteria and Reporting

Checking test logs against the exit criteria specified in test planning

Evaluation Exit Criteria and Reporting

Assessing if more tests are needed or if the exit criteria specified should be changed

Evaluation Exit Criteria and Reporting

Writing a test summary report for stakeholders

Test Closure

Checking which planned deliverables have been delivered

Test Closure

Closing incident reports or raising change records for any that remain open

Test Closure

Documenting the acceptance of the system

Test Closure

Finalizing and archiving testware, the test environment and the test infrastructure for later reuse

Test Closure

Handing over the testware to the maintenance organization

Test Closure

Analyzing lessons learned to determine changes needed for future releases and projects