Software Test Documentation

by Nataliia Vasylyna | March 18, 2016 7:34 am

To run into production the system of a very high quality, QA specialists perform a thorough checking of every aspect of the system or application with the help of various testing types (automated or manual testing[1], security control, usability testing[2], load testing, unit testing[3], etc.).

The testing procedure requires the creation of several documents which will arrange the whole process and ensure a complete checking.

What Documents Can Be Used During Software Testing?

• Test plan
• Test design specification
• Test case
• Test procedure specification
• Test item transmittal report
• Test log
• Test incident report
• Test summary report

The first four documents are created before software testing process and even before development procedure. They are necessary to perform scripted testing which presupposes the planning of tests based on the formal system requirements.

It is not obligatory and necessarily to create all mentioned documents to check one product or one of its aspects. The choice depends on the product peculiarities, the specialists and the internal regulations of the company.

Each document of the given list consists of several elements or sections. These elements are used to describe and define the conditions of testing environment, the specific feature to be tested, the input combinations, etc.

To properly write every document used during software testing, a tester should be aware of the peculiarities of its constituent parts and their goals.

Related Posts:

• Test Design Specification[4]
• Does Your Project Need a Test Plan?[5]
• Test Plan Constituents[6]

Source URL: https://blog.qatestlab.com/2016/03/18/software-testing-documents/

---