chapter 7e csta cstp test closure

Post on 12-May-2017

215 Views

Category:

Documents

2 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Test Closure

Introduction

Test Closure Entry Criteria Test Closure Exit Criteria

Test Summary Reports Critical Issue Encountered

Introduction

• Final phase in STLC.• Ensures that all the testing activities are performed in

adherence to the Test Plan.• Decides whether the project can be moved into the

production phase or not. (means Go/No Go Decision)

Introduction

Test Closure Entry Criteria Test Closure Exit Criteria

Test Summary Reports Critical Issue Encountered

Entry Criteria of Test Closure

Scope/Objective should be completed

Defect status should be closed.

All Test cases should be executed.

All the test cases should mapped to the Req

Entry Criteria of Test Closure

Introduction

Test Closure Entry Criteria Test Closure Exit Criteria

Test Summary Reports Critical Issue Encountered

Test Summary Report

Critical Issue Encounter

Exit Criteria of Test Closure

Test Closure Exit Criteria

Introduction

Test Closure Entry Criteria Test Closure Exit Criteria

Test Summary Reports Critical Issue Encountered

• It contains the following information,• Total No. of Testcases• Total No. of Testcases executed• No. of Testcases failed• No. of failed Testcases has been fixed• No. of Testcases has been rejected and deferred.

Test Summary Reports

Content of Test Summary Reports1. Test summary Reports

a) Details Of the Build/Runsb) Types of testing Conductedc) Test Environment/Tools Usedd) Items to be Tested and Items Not to be Tested

2. Test Resultsa) Metrics Generated

i. Test Management Metricsii. Test Coverage Metricsiii. Defect Metrics

b) Assessment of Quality3. Test deliverables

a) Known Issuesb) Recommendation

Contents of Test Summary Reports with Examples

1. Test summary Reportsa) Details Of the Build/Runs. (Scope Of Build)b) Types of testing Conducted. (Functional Or Non

Functional testing)c) Test Environment/Tools Used. ( Server, Platform,

Configuration and Tool used for testing)d) Items to be Tested and Items Not to be Tested.

2. Test Resultsa) Metrics Generated

i. Test Management Metrics. (Total no of Bug Fixes, Total No of Enhancements, No of Bugs/Enhancements covered in Test Cases, Test case Design Productivity, Test Execution Productivity, Requirement Stability index)

ii. Test Coverage Metrics. (Total test cases-Functional and Regression test cases, Test case in Scope, Total Test case Passed, Total Test Case Failed, Total no of Test case Non-executed, Total Executed Test Cases, Test Coverage (At the End of the Sprints) , Pass percentage (At the End of the Sprints)

iii. Defect Metrics. (Defect Status and Severity, Defect Trend)

2. b) Assessment of Quality. (Acceptable, Quality Index- System Stability)

3. Test deliverables– Test Cases designed as part of bugs/enhancements– Test Log/Test Summary Results– Requirement Traceability Matrix

a) Known Issuesb) Recommendation

Introduction

Test Closure Entry Criteria Test Closure Exit Criteria

Test Summary Reports Critical Issue Encountered

Critical Issue Encountered

The issues that were encountered by the testing team are identified and discussed.

The resolutions for the critical issues are documented.

Unresolved outstanding issues are listed out.

top related