4 Types of Project Documentation

by Nataliia Vasylyna | May 7, 2014 10:00 am

It is hard and not so efficient to perform web site testing, desktop testing or mobile application testing without any documentation.

Even if there are test-cases it may be difficult for a tester to make sense of some features and functions of a software product, to understand why the things are done this way and not the other way. Besides nowadays test-cases aren’t always used in course of mobile testing.

That is why a software testing company recommends its testers to utilize diverse documents.

The Documents That are Useful for Testing Activities Are:

1. Guidance Manual. It explains how to work with the program and peculiarities of its functions and features. If there is such an opportunity, it is useful to communicate with the technicians who created the guidance manual.
2. Guidance for Testers. Such documents are elaborated by testers in order to enable other testers to check the software or its areas quickly. Such guidances may contain short videos. Video instructions are easy to create and re-record, unlike texts. That is why video instructions are widely used for mobile testing.
3. Setup Instructions. These documents are useful when exact following certain requirements is compulsory or exact data must be used. For example, generating certain data.
4. Reference Documents. Such documents give information about what and where can be found, contact information of project parties, explain how to acquire and install a new software build and so on.

Related Posts:

• What we learned from 100,000 game bugs reported?[1]
• Guide for QA Leads: Responsibilities, Skills, Team Management[2]
• Best Practices of Test Case Creation in JIRA[3]

Source URL: https://blog.qatestlab.com/2014/05/07/4-types-of-documents-that-should-be-utilized-during-software-testing/

---