Answer / ronh

[Company Logo]






Test Exit Report
Version 0.0

Description of Project















DOCUMENT NO:
VERSION:

CONTACT: [name]
EMAIL:

DATE: 3/30/2009








Distribution is subject to copyright.

Disclaimers
The information contained in this document is the
proprietary and exclusive property of [Company Name] except
as otherwise indicated. No part of this document, in whole
or in part, may be reproduced, stored, transmitted, or used
for design purposes without the prior written permission of
[Company Name].
The information contained in this document is subject to
change without notice.
The information in this document is provided for
informational purposes only. [Company Name] specifically
disclaims all warranties, express or limited, including,
but not limited, to the implied warranties of
merchantability and fitness for a particular purpose,
except as provided for in a separate software license
agreement.
Privacy Information
This document may contain information of a sensitive
nature. This information should not be given to persons
other than those who are involved in the Project Name
project or who will become involved during the lifecycle
Trademarks
[Trademarks are added here]
Version History


REVISION CHART
Version Author(s) Description of Version Date
Completed









Document Owner
•
The primary contact for questions regarding this document
is:
Author:
Project Name
Phone:
Email:
Document Approval

Document Name:
Publication Date:
Contract Number:
Project Number:
Prepared by:

Approval: __________________________
Name and Organization

Concurrence: _________________________
Name and Organization

Table of Contents
1 Introduction 5
1.1 Objectives 5
1.2 Notification of Test Exit 5
1.3 Notification 5
1.4 Defects and Test Case Summary Information 6
1.5 Test Case Listing 6
1.6 Test Case Status 7
1.7 Defects Remaining in this Release 7
1.8 Defects Determined to be Invalid 8
1.9 Exceptions 8
1.10 Actual Versus Projected Defect Chart 9
1.11 Software Release Form 10

SOFTWARE RELEASE FORM 10


Index of Tables

Table 1 — Test Case Summary 6
Table 2 — Test Case Listing 6
Table 3 — Test Case Status 7
Table 4 — Test Cases with Remaining Defects 7
Table 5 — Invalid Test Cases 8
Table 6 — Defects Deferred to a Later Release 8
Figure 1 — Actual Versus Projected Defect Chart 9

1 Introduction
The Test Exit Report outlines the findings of all testing
activities. It identifies the items and features tested;
and reports the number of test cases that passed, failed,
or were found to be obsolete and reports the findings to
project management.

1.1 Objectives
Describe the high-level test plan objectives, of the
products to be delivered.

1.2 Notification of Test Exit

Date
Application
Release
Test Level
Business Area Manager
Project Executive
Application Owner
Solution Project Manager
Test Leader


1.3 Notification
The application described above completed the:
[ ] Installation [ ] Integration
[ ] Function [ ] System
[ ] Customer Acceptance
On this date:
____________________________________________________________
_____
Using a [ ] Manual [ ] Automated testing method on Release
Version: __________________
As stated in the Master Test Plan, Testing was limited to
the new change requests and pre-existing defects included
in the scope of this release. All planned test cases have
been performed, and all Defects have either been fixed and
verified, or deferred to a future release. The application
will now exit from testing with the following exceptions.
Please confirm that you are in agreement.

1.4 Defects and Test Case Summary Information
The following illustrates the Defect and Test Case status
at the time of test exit.

Total Number of Test Cases Total Passed Total Failed
Total Defects that are still Remaining Total
Invalid Test Cases Total Exceptions for Later Release

Table 1 — Test Case Summary


1.5 Test Case Listing
Obsolete or Invalid
N/A Test Case Number – Title
N/A Test Case Number – Title
N/A Test Case Number – Title
N/A Test Case Number - Title
N/A Test Case Number - Title
N/A Test Case Number - Title
Passed
100% complete Test Case Number – Title
100% complete Test Case Number – Title
100% complete Test Case Number – Title
100% complete Test Case Number – Title
100% complete Test Case Number – Title
100% complete Test Case Number – Title
100% complete Test Case Number – Title
100% complete Test Case Number – Title
Failed
0% complete Test Case Number – Title
0% complete Test Case Number - Title
0% complete Test Case Number – Title
0% complete Test Case Number - Title
Table 2 — Test Case Listing



1.6 Test Case Status

Test Case Number Test Case Title Test Date
Status Regression Test Date Status
101 Test Case 1 11/20/2007 Passed
102 Test Case 2 11/20/2007 Failed 11/21/2007
Passed







Table 3 — Test Case Status

1.7 Defects Remaining in this Release
These are the defects that were NOT FIXED with this
software release. After management review, the following
defects were determined to be acceptable for release with
this version of the software. There are deferred defects.

Test Case Number Test Case Title Date Tested
Defect Reason






Table 4 — Test Cases with Remaining Defects



1.8 Defects Determined to be Invalid
These are the defects logged that were determined to be
invalid. They were either not reproducible, a result of a
configuration error in the test environment, or a
misunderstanding of the requirement. There are no deferred
defects.

Test Case Number Test Case Title Date Tested
Invalid Reason






Table 5 — Invalid Test Cases



1.9 Exceptions
The following defects have been specifically deferred to a
later release. They were deferred because the defect
updates were reviewed and decided that these updates are
not being addressed in this release. There are deferred
defects.

Test Case Number Test Case Title Date Tested
Reason for Deferral





Table 6 — Defects Deferred to a Later Release




1.10 Actual Versus Projected Defect Chart

Note: The following chart displays the Actual number of
defects versus the Projected number estimated prior to the
start of testing.



Figure 1 — Actual Versus Projected Defect Chart















1.11 Software Release Form

[COMPANY LOGO]
SOFTWARE RELEASE FORM
QA Department Manager Signature:
Date:
Business Analyst Signature:
Date:
Software Release Name:
Software Version #:
Client Company:


The following software:
_______________________________________________ has been
tested by the [Company Name] Quality Assurance Department
and meets the criteria to be deployed into production.

A complete Test Exit Report is on file with the [Company
Name] Quality Assurance Department and may be reviewed upon
request.


Release to Production is:
[ ] Disapproved
[ ] Approved

what is the SOAP UI and Web services? what are the uses in testing?

0 Answers   IBM,

---

What are test documents and what it includes?

1 Answers  

---

Tell me some of the test cases for Notepad Application?

2 Answers   Logica CMG,

---

What is the difference between black box and white box testing?

0 Answers  

---

How would you define Quality Assurance?

4 Answers   Ordain Solutions,

---

---

What is the differnt between Test condition and TesT Scenario

1 Answers  

---

different between bitmap checkpoint and image checkpoint ?

1 Answers  

---

how we apply cmmi and iso in oyr testing or qa do it have some specifuc format

0 Answers  

---

What kind of documentation is required for QA,QC and testing.?Tell me the diffrence between QA,QC and testing

4 Answers   Tvs Lucas,

---

if the requrements are not there in the specifications then how will you write the test scenario& test Cases

7 Answers   Covansys, QA,

---

What is code walkthrough?

0 Answers  

---

what is metrics? type of metrics?

9 Answers   Infosys, MRS,

---