How to Document Test Procedure Correctly?

by Nataliia Vasylyna | August 21, 2013 10:00 am

Every tester knows that test-procedure is a very important component of any mobile testing, desktop testing or web site testing. The success of a testing process depends on its proper elaboration and documentation.

Testing documents must not be treated as static. They change during the application development process. So, test procedure must be adjustable, it should be easy to make necessary changes in it.

If a test procedure is very thorough, contains URLs and detailed steps to perform test-cases, it will take a lot of time and efforts to make even minor changes in the data.

That is why a software testing company prefers to keep specific test data in a separately recorded test-case scenarios and databases. It is a good idea to keep data dictionary. Testers will be able to consult them choosing suitable input data for the test-cases.

To make a test-procedure maintainable, one should avoid details. It is better to make references on the dictionary and the database containing boundaries of input data. But the dictionary and the database should be separated from the test procedure.

Such test-procedure structure is especially convenient for automated testing and can be used as a basis for creating test-procedures for similar projects.

Anyway, it is better both for manual and automated testing if the test-procedure is distinct and easily maintainable.

Learn more from QATestLab

Related Posts:

Endnotes:
  1. Test Design Specification: https://blog.qatestlab.com/2020/05/15/test-design-specification/
  2. Testing at a Complex Project: QATestLab Real Case: https://blog.qatestlab.com/2019/09/03/complex-project-testing/
  3. How to Create Efficient QA Team in Startup: https://blog.qatestlab.com/2019/03/29/qa-in-startup/

Source URL: https://blog.qatestlab.com/2013/08/21/how-to-document-test-procedure-correctly/