1. TEST PLANNING
1.1. Test Activities
1.1.1. Define objectives of testing
1.1.2. The approach for meeting the objectives
1.1.3. test plans might be revisited
1.2. Work Products
1.2.1. test strategy
1.2.2. test plan/s
1.2.3. entry and exit criteria
1.2.4. traceability info (charts, matrixes, diagrams, etc.)
1.2.5. test execution schedule
2. TEST MONITORING AND CONTROL
2.1. Test Activities
2.1.1. Checking test results and logs against specified coverage criteria
2.1.2. Assessing the level of component or system quality based on test results and logs
2.1.3. Determining if more tests are needed
2.2. Test Work Products
2.2.1. products include management concerns incl. budgeting, time and effort spent, etc.
2.2.2. test progress reports (ongoing)
2.2.3. test summary reports (milestones)
3. TEST ANALYSIS (what to test)
3.1. Test Activities
3.1.1. Analyzing the test basis: Business, functional, system requirements, user stories, epics, use cases;
3.1.2. Risk analysis reports, which may consider functional, non-functional, and structural
3.1.3. Design and implementation information, code, database; metadata and queries, and interfaces
3.1.4. Evaluating the test basis and test items to identify defects of various types, such as:
3.1.5. Ambiguities, Omissions, Inconsistencies, Inaccuracies, Contradictions, Superfluous statements
3.2. Test Work Products
3.2.1. defined and prioritized test conditions (tracable to specific elements of the test basis they cover)
3.2.2. Reporting of defects in test basis
3.2.3. Test charters (for exploratory testing)
4. TEST IMPLEMENTATION
4.1. Test Activities
4.1.1. Developing and prioritizing test procedures, and, potentially, creating automated test scripts
4.1.2. Creating test suites from the test procedures and (if any) automated test scripts
4.1.3. Arranging the test suites within a test execution schedule in a way that results in efficient test execution
4.1.4. 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
4.1.5. Preparing test data and ensuring it is properly loaded in the test environment
4.1.6. Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test suites
4.2. Test Work Products
4.2.1. Test procedures and the sequencing of those test procedures
4.2.2. Test suites
4.2.3. A test execution schedule
5. TEST EXECUTION
5.1. Test Activities
5.1.1. Recording the IDs and versions of the test item(s) or test object, test tool(s), and testware
5.1.2. Executing tests either manually or by using test execution tools
5.1.3. Comparing actual results with expected results
5.1.4. Analyzing anomalies to establish their likely causes
5.1.5. Reporting defects based on the failures observed
5.1.6. Logging the outcome of test execution (e.g., pass, fail, blocked)
5.1.7. Repeating test activities either as a result of action taken for an anomaly, or as part of the planned testing
5.1.8. Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test results
5.2. Test Work Products
5.2.1. Documentation of the status of individual test cases or test procedures (e.g., ready to run, pass, fail, blocked, deliberately skipped, etc.)
5.2.2. Defect reports
5.2.3. Documentation about which test item(s), test object(s), test tools, and testware were involved in the testing
6. TEST COMPLETION
6.1. Test Activities
6.1.1. 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
6.1.2. Creating a test summary report to be communicated to stakeholders
6.1.3. Finalizing and archiving the test environment, the test data, the test infrastructure, and other testware for later reuse
6.1.4. Handing over the testware to the maintenance teams, other project teams, and/or other stakeholders who could benefit from its use
6.1.5. Analyzing lessons learned from the completed test activities to determine changes needed for future iterations, releases, and projects
6.1.6. Using the information gathered to improve test process maturity
6.2. Test Work Products
6.2.1. Test summary reports
6.2.2. Action items for improvement of subsequent projects or iterations
6.2.3. Change requests
6.2.4. Product backlog items
6.2.5. Finalized testware
7. TEST DESIGN
7.1. Test Activities
7.1.1. Designing and prioritizing test cases and sets of test cases
7.1.2. Identifying necessary test data to support test conditions and test cases
7.1.3. Designing the test environment and identifying any required infrastructure and tools
7.1.4. Capturing bi-directional traceability between the test basis, test conditions, and test cases
7.2. Test Work Products
7.2.1. test cases
7.2.2. sets of test cases
7.2.3. the design and/or identification of the necessary test data
7.2.4. the design of the test environment
7.2.5. the identification of infrastructure and tools