During the testing process, the people involved generate documents and scripts that include every detail of the test process. You will find information about the inputs, expected results, requirements of the end user, test script, databases and other software details. This information is called testware and is also popularly known as a testing tool. These documents are essential. It is a good practice because the entire team can use them. Anyone joining the project in the middle can refer to the testware and get a hold of the tasks before making a contribution. It might sound like a general software document, but it is entirely different. Factors that make it different are: Testers develop this document only for a specific purpose. The metrics in this document differ in quality and are focused on the end-user requirements. So, in a nutshell, you can call it a document having all the prerequisites to perform the tests on the software under question. Additionally, it has the results or the responses recorded while performing the tests.