Please enable JavaScript.
Coggle requires JavaScript to display documents.
Test process - Coggle Diagram
Test process
Is sets of test activities
Test planning
Objectives
May be revisited based on feedback from monitoring and control activities
Define the objectives of testing and the approach for meeting test objectives
Work product
Information about the test basis
Exit criteria
Test monitoring and control
Objectives
Control: Taking actions necessary to meet the
objectives of the test plan
Evaluation of exit criteria for test execution
Provide test progress report
Monitoring: Comparison of actual progress against planned progress
Work product
Test progress report
Test summary report (produced at various completion milestones)
Test analysis
Objectives
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
Analyzing the test basis appropriate to the test level being considered
Capturing bi-directional traceability between each element of the test basis and the associated test conditions
Work product
Defined and prioritized test conditions
Test design
Objectives
Designing and prioritizing test cases and sets of test cases
Identifying necessary test data to support test conditions and test cases
Designing the test environment and identifying any required infrastructure and tools
Capturing bi-directional traceability between the test basis, test conditions, and test cases
Work product
High-level test cases
Bi-directionally traceable to the test condition(s)
The design of the test environment
The identification of infrastructure and tools
Test implementation
Objectives
Developing and prioritizing test procedures, and potentially, creating automated test scripts
Creating test suites from the test procedures and (if any) automated test scripts
Building the test environment and verifying that everything needed has been set up
Preparing test data and ensuring it is properly loaded in the test environment
Verifying and updating bi-directional traceability between the test basis, test conditions, test
cases, test procedures, and test suites
Work product
Test procedures
Test suites
A test execution schedule
The test data
The concrete expected results
Test execution
Objectives
Recording the IDs and versions of the test item(s) or test object, test tool(s), and testware
Executing tests either manually or by using test execution tools
Comparing actual results with expected results
Analyzing anomalies to establish their likely causes
Reporting defects based on the failures observed
Logging the outcome of test execution
Repeating test activities either as a result of action taken for an anomaly, or as part of the planned testing
Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test results
Work product
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
Test completion
Objectives
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
Creating a test summary report to be communicated to stakeholders
Finalizing and archiving the test environment, the test data, the test infrastructure, and other testware for later reuse
Handing over the testware to the maintenance teams, other project teams, and/or other stakeholders who could benefit from its use
Using the information gathered to improve test process maturity
Analyzing lessons learned from the completed test activities to determine changes needed for future iterations, releases, and projects
Work product
Test summary reports
Action items for improvement of subsequent projects or iterations
Change requests or product backlog items
Finalized testware
Depends on the context
Software development lifecycle model and project methodologies being used
Test levels and test types being considered
Product and project risks
Business domain
Operational constraints, including but not limited to:
Budgets and resources
Timescales
Complexity
Contractual and regulatory requirements
Organizational policies and practices
Required internal and external standards