Main activities of test process

Scheduling test activities, assigning resources for the activities

Analyzing the test basis appropriate to the test level being considered

Arranging the test suites within a test execution schedule in a way that results in efficient test execution

Comparing actual results with expected results

involves taking actions necessary to meet the objectives of the test plan

Defining and prioritizing test conditions for each feature based on analysis of the test basis, and considering functional, non-functional, and structural characteristics, other business and technical factors, and levels of risks

Preparing test data and ensuring it is properly loaded in the test environment

Analysing anomalies to establish their likely causes (e.g., failures may occur due to defects in the code, but false positives also may occur)

Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test suites

Logging the outcome of test execution (e.g., pass, fail, blocked)

Analyzing lessons learned from the completed test activities to determine changes needed for future iterations, releases, and projects

Checking whether all defect reports are closed, entering change requests or product backlog items for any defects that remain unresolved at the end of test execution

Repeating test activities either as a result of action taken for an anomaly, or as part of the planned testing (e.g., execution of a corrected test, confirmation testing, and/or regression testing)

Developing and prioritizing test procedures, and, potentially, creating automated test scripts

Capturing bi-directional traceability between the test basis, test conditions, test cases, and test procedures

Handing over the testware to the maintenance teams, other project teams, and/or other stakeholders who could benefit from its use

Reporting defects based on the failures observed 

Creating a test summary report to be communicated to stakeholders

Building the test environment (including, potentially, test harnesses, service virtualization, simulators, and other infrastructure items) and verifying that everything needed has been set up correctly

Checking whether all defect reports are closed, entering change requests or product backlog items for any defects that remain unresolved at the end of test execution

Identifying necessary test data to support test conditions and test cases

Creating test suites from the test procedures and (if any) automated test scripts

Evaluating the test basis and test items to identify defects of various types (Ambiguities, Omissions, Inconsistencies, Inaccuracies, Contradictions, Superfluous statements)

Selecting metrics for monitoring and controlling

on-going comparison of actual progress against the test plan using any test monitoring metrics defined in the test plan.

Defining the amount, detail, template for the documentation

Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test results.

Using the information gathered to improve test process maturity

Identifying features and sets of features to be tested

involves taking actions necessary to meet the objectives of the test plan

Designing the test environment and identifying any required infrastructure and tools

Determining the scope and risks and identifying the objective of testing

Capturing bi-directional traceability between each element of the test basis and the associated test conditions

Defining entry and exit criteria

Recording the IDs and versions of the test item(s) or test object, test tool(s), and testware

Checking whether all defect reports are closed, entering change requests or product backlog items for any defects that remain unresolved at the end of test execution

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

Executing tests either manually or by using test execution tools

Designing and prioritizing test cases and sets of test cases

Defining the overall approach of testing

Using the information gathered to improve test process maturity

Deciding about automation

Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test results.

Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test suites