Test progress monitoring and control Chapter 5 Part 2 3. Test - PowerPoint PPT Presentation

INF 3121 Software Testing Test progress monitoring and control Chapter 5 – Part 2 3. Test progress monitoring and control 4. Configuration management 5. Risk and testing 6. Incident management

Test progress monitoring and 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader control and tester 2. Test planning and estimation • 2.1 Test planning • 2.2 Test planning activities • 2.3 Entry criteria • 2.4 Exit criteria  LO: Recall common metrics used tor test • 2.5 Test estimation • 2.6 Test strategy, test preparation and execution approach 3. Test progress monitoring and  LO: Explain and compare metrics used for test control • 3.1 Test progress monitoring reporting (e.g.: defects found & fixed, tests passed • 3.2 Test reporting & failed) • 3.3 Test control 4. Configuration management  LO: Summarize the content of the test summary 5. Risk and testing report, according to IEEE-829 • 5.1 Project risks • 5.2 Product risks 6. Incident management

Test progress monitoring 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader and tester 2. Test planning and estimation • 2.1 Test planning • The purpose of test monitoring is to give feedback and visibility • 2.2 Test planning activities • 2.3 Entry criteria about test activities. • 2.4 Exit criteria • 2.5 Test estimation • 2.6 Test strategy, test approach • Information to be monitored may be collected manually or 3. Test progress monitoring and automatically and may be used to measure exit criteria, such as control • 3.1 Test progress monitoring coverage. • 3.2 Test reporting • 3.3 Test control • Metrics may also be used to assess progress against the planned 4. Configuration management schedule and budget. 5. Risk and testing • 5.1 Project risks • 5.2 Product risks 6. Incident management

Test progress monitoring 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader and tester 2. Test planning and estimation • 2.1 Test planning • 2.2 Test planning activities • 2.3 Entry criteria • 2.4 Exit criteria % of work done in test % of work done in test • 2.5 Test estimation Dates of test milestones. • 2.6 Test strategy, test case preparation environment preparation . approach 3. Test progress monitoring and control • 3.1 Test progress monitoring Testing costs, including the Test case execution (e.g. Defect information (e.g. • 3.2 Test reporting cost compared to the number of tests run/not defect density, defects • 3.3 Test control benefit of finding the next run) found and fixed). defect or to run the next 4. Configuration management test . 5. Risk and testing • 5.1 Project risks Test coverage of Subjective confidence of • 5.2 Product risks requirements, risks or testers in the product. code. 6. Incident management

Test log - template 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader and tester 2. Test planning and estimation • 2.1 Test planning • 2.2 Test planning activities • 2.3 Entry criteria • 2.4 Exit criteria • 2.5 Test estimation • 2.6 Test strategy, test approach 3. Test progress monitoring and control • 3.1 Test progress monitoring • 3.2 Test reporting • 3.3 Test control 4. Configuration management 5. Risk and testing • 5.1 Project risks • 5.2 Product risks 6. Incident management

Test case summary 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader and tester 2. Test planning and estimation • 2.1 Test planning • 2.2 Test planning activities • 2.3 Entry criteria • 2.4 Exit criteria • 2.5 Test estimation • 2.6 Test strategy, test approach 3. Test progress monitoring and control • 3.1 Test progress monitoring • 3.2 Test reporting • 3.3 Test control 4. Configuration management 5. Risk and testing • 5.1 Project risks • 5.2 Product risks 6. Incident management

Total defects opened and closed chart 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader and tester 2. Test planning and estimation • 2.1 Test planning • 2.2 Test planning activities • 2.3 Entry criteria • 2.4 Exit criteria • 2.5 Test estimation • 2.6 Test strategy, test approach 3. Test progress monitoring and control • 3.1 Test progress monitoring • 3.2 Test reporting • 3.3 Test control 4. Configuration management 5. Risk and testing • 5.1 Project risks • 5.2 Product risks 6. Incident management

Test reporting 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader and tester Test reporting is concerned with summarizing information about the 2. Test planning and estimation • 2.1 Test planning testing endeavor, including: • 2.2 Test planning activities • 2.3 Entry criteria • 2.4 Exit criteria • 2.5 Test estimation • 2.6 Test strategy, test approach Analyzed metrics to 3. Test progress monitoring and What happened during support decisions control • 3.1 Test progress monitoring a period of testing about future actions • 3.2 Test reporting (ex: dates when exit (ex: the economic • 3.3 Test control criteria were met) benefit of continued 4. Configuration management testing) 5. Risk and testing • 5.1 Project risks • 5.2 Product risks 6. Incident management * The outline of a test summary report is given in ‘Standard for Software Test Documentation’ (IEEE 829).

Test reporting 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader and tester 2. Test planning and estimation Metrics are collected at the end of a test level in order to assess: • 2.1 Test planning • 2.2 Test planning activities • 2.3 Entry criteria The adequacy of the test objectives for that test level • 2.4 Exit criteria • 2.5 Test estimation • 2.6 Test strategy, test approach The adequacy of the test approaches with respect to its objectives 3. Test progress monitoring and control • 3.1 Test progress monitoring The effectiveness of the testing with respect to its objectives • 3.2 Test reporting • 3.3 Test control 4. Configuration management 5. Risk and testing • 5.1 Project risks • 5.2 Product risks 6. Incident management

Test reporting 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader and tester 2. Test planning and estimation • 2.1 Test planning • 2.2 Test planning activities • 2.3 Entry criteria • 2.4 Exit criteria • 2.5 Test estimation • 2.6 Test strategy, test approach 3. Test progress monitoring and control • 3.1 Test progress monitoring • 3.2 Test reporting • 3.3 Test control 4. Configuration management 5. Risk and testing • 5.1 Project risks • 5.2 Product risks 6. Incident management

Test summary report - template 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader and tester 2. Test planning and estimation • 2.1 Test planning • 2.2 Test planning activities • 2.3 Entry criteria • 2.4 Exit criteria • 2.5 Test estimation • 2.6 Test strategy, test approach 3. Test progress monitoring and control • 3.1 Test progress monitoring • 3.2 Test reporting • 3.3 Test control 4. Configuration management 5. Risk and testing • 5.1 Project risks • 5.2 Product risks 6. Incident management

Test progress monitoring 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader and tester Test control describes any guiding or corrective actions taken as a result 2. Test planning and estimation • 2.1 Test planning of information and metrics gathered and reported. • 2.2 Test planning activities • 2.3 Entry criteria • 2.4 Exit criteria • 2.5 Test estimation Examples of test control actions are: • 2.6 Test strategy, test approach 3. Test progress monitoring and Making decisions based on information from test monitoring control • 3.1 Test progress monitoring • 3.2 Test reporting • 3.3 Test control Re-prioritize tests when an identified risk occurs 4. Configuration management 5. Risk and testing • 5.1 Project risks Change the test schedule due to availability of a test environment • 5.2 Product risks 6. Incident management Set an entry criterion requiring fixes to have been retested (confirmation tested) by a developer before accepting them into a build

Configuration management 1. Test organization • 1.1 Test organization and independence • 1.2 Tasks of the test leader and tester 2. Test planning and estimation • 2.1 Test planning • 2.2 Test planning activities • 2.3 Entry criteria • 2.4 Exit criteria • 2.5 Test estimation  LO: Explain why configuration • 2.6 Test strategy, test approach management is necessary in software 3. Test progress monitoring and development and testing control • 3.1 Test progress monitoring • 3.2 Test reporting  LO: Enumerate software artifacts that • 3.3 Test control need to be under configuration 4. Configuration management management 5. Risk and testing • 5.1 Project risks • 5.2 Product risks 6. Incident management