Release Report Template - © www.SoftwareTestingHelp.com

Release ID: Release Name: Customer: Project Manager:

Start Date Planned: Actual Start Date: End Date Planned: Actual End Date: DD-MM-YYYY DD-MM-YYYY DD-MM-YYYY DD-MM-YYYY Sample Release Report Template (By http//:www.SoftwareTestingHelp.com)

1. Scope

<>

2. References

<>

3. Release Description

This release is a controlled release of <> and contains following features and functionalities.

The features marked in * are new in this release.

1. Module 1 1.1 Feature 1 1.1.1 Functionality 1 1.1.2 Functionality 2 1.2 Feature 2 1.2.1 Functionality 1 1.2.2 Functionality 2 1.2.3 Functionality 3*

2. Module 3 2.1 Feature 1 2.1.1 Functionality 1 2.1.2 Functionality 2 1.2 Feature 2 2.2.1 Functionality 1 2.2.2 Functionality 2 2.2.3 Functionality 3

3. Module 3* 3.1 Feature 1* 3.1.1 Functionality 1* 3.1.2 Functionality 2*

The following features are not been implemented in this release.

1. Module 1 Release Report Template - © www.SoftwareTestingHelp.com

1.1 Feature 1 1.1.1 Functionality 1

4. Configuration Management

We are using <> as configuration management tool. The build is available in the following path.

Internal Link: <>

External Link: <>

5. Installation Instructions and Steps

<>

6. Issues / Bugs Fixed

The status of the bugs is updated in <>.

7. Issues / Bugs To Be Fixed

Sl.No Bug ID Bug / Issue Description Remarks (If any)

1.

2.

8. Deliverables

Sl.No Deliverable Medium Status Remarks

1.

2.

3.

9. Known Bugs / Issues Sl.No. Bug / Issue Description Test Case Schedule to Remarks (If any) ID Fix

1.

2.

3. Release Report Template - © www.SoftwareTestingHelp.com

10. Release Check List

Sl.No Description Y / N

1. Have all the files been checked in <>?

2. Has the label been put on the proper folder in <> as per internal standards?

3. Is the release identifiable as 'external' / 'internal' release in <>?

4. In the comments, has the version been mentioned in <>?

5. In the comments, has a short description been mentioned in <>?

6. Code has been reviewed and code review issues are logged in <>?

7. Code review checklist has been updated and available in <>?

8. Unit test document has been prepared and reviewed?

9. Unit test cases executed and the results updated for the status?

10. Updated unit test case document is available in <>?

11. All the <> issues for this released has been resolved/closed?

12. All the work package tasks completed and updated in <>?

13. Is Smoke testing done and passed?

(by http//:www.SoftwareTestingHelp.com)