Test case document, Bug report, Status reports, Tracebility
Matrix, Use cases, Metric preparation, Release report

1.Test Plan : A formal test plan is a document that 
provides and records important information about a test 
project, for example: Resources, Schedule & Timeline, Test 
Milestones, Use cases and/or Test cases 
2.Test Case: A set of test inputs, execution conditions and 
expected results.
3.Test Data: The actual (set of) values used in the test or 
that are necessary to execute the test.
4.Test Scripts: is used to test a particular functionality 
(business rule). It may consist of 1 or more Test Cases.
5.Test Log: A chronological record of all relevant details 
about the execution of a test 
6.Bug Reports: Contains a summary of the bug, its priority 
and other details regarding the bug.

BRD   business requirment document.
srs   system requirment specifications.
frs   functional requirment specifications,
Test plan:  it include what to test,when to test ,where to 
test, whom to test,how to test.
test cases : functionality to be test
defwct reporting : 
bug report  :

Here I ma giving all the documents,which are using in our 
project and the authorized person,who is preparing them.It 
varies from company to company.

Project Plan:Prepared by PM.
QA-Project Plan:Prepared by QA Manager
Test Reports:Generally prepared by Team lead for every 
release.
Software Metrics:Team Lead
Module based Test Plan:Testing engineer
Test Results:Test Engineer
Testcase document:Test Engineer
Defect Matrix:Prepared by Team Lead
Traceability Matrix:Team Lead or team member
Bu Reports: Prepared by test engineer.

Types of documents prepared during testing:
1)KT document
2)Ambiguity document(issues or doubts raised by testers are 
collected in this doc)
3)Requirement Traceability Matrix
4)Test Plan
4)Test Case doc
5)Test Log
6)Status Reports
7)Defect Summary Report
8)Defect Traceability Matrix
9)Test Summary Report