Contents of test report

There are two documents,which should be prepared at
particular phase.
1.Test Results document.
2.Test Report document.

Test Results doc will be prepared at the phase of each type
of Testing like FULL FUNCTIONAL TEST PASS,REGRESSION TEST
PASS,SANITY TEST PASS etc...Test case execution against
the application.Once you prepared this doc,we will send the
doc to our TL and PM.By seeing the Test Results doc ,TL
will come to know the coverage part of the test case.Here I
am giving you the contents used in the Test Results doc.

1.Build No
2.Version Name
3.Client OS
4.Feature set
5.Main Feature
6.Defined Test cases on each feature.
7.QA engineer Name
8.Test cases executed.(Includes pass and fail)
9.Test cases on HOLD(Includes blocking test cases and
deferred Test cases)
10.Coverage Report(Which includes the coverage ratings in
% ,like % of test cases covered,% of test cases failed)

Coming to Test report,generally we will prepare Test
report ,once we rolled out the product to our client.This
document will be prepared by TL and delivered to
the client.Mainly,this document describes the what we have
done in the project,achievements we have reached,our
leanings in throughout the project etc...The other name
for Test report is Project Closure Report and we will
summarize the all the activities,which have taken place in
through out the project.Here I am giving your the contents
covered in the Test Report.
1.Test Environment(Should be covered the OS,Application or
web servers,Machine names,Database,etc...)
2.Test Methods(Types of Tests,we have done in the project
like Functional Testing,Platform Testing,regression
Testing,etc..
3.Major areas Covered.
4.Bug Tracking Details.(Includes inflow and outflow of the
bus in our delivered project)
5.Work schedule(When we start the testing and we finished)
6.Defect Analysis
6.1 Defects logged in different types of tests like
Functional Test,regression Test as per area wised.
6.2 State of the Defects at end of the Test cycle.
6.3 Root cause analysts for the bugs marked as NOT A BUG.
7.QA observations or learning through the life cycle.