What Test Procedure Pattern Should Be Like?

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

Test-procedure is a very important component of any testing process. Its proper elaboration ensures success of any mobile application testing, desktop testing or web site testing.

Every testing process has its peculiarities, but some elements are common for all of them. It’s a good practice for a software testing company to use a test-procedure pattern.

Usually a Test-Procedure Pattern Should Include:

1. Test- procedure ID that is commonly created basing on requirement use cases.
2. Test title that describes the object under test.
3. Implementation date indicating the day when the test-procedure was performed.
4. Name of the tester performing the test-procedure.
5. Name of the tester who elaborated the test-procedure.
6. Short description of the testing process aim.
7. Catalogue of example uses that are tested under this test objective.
8. Preliminary condition that must be satisfied before executing the procedure.
9. Test-procedure verification technique.
10. User behavior. This field clarifies the aim of the test-procedure.
11. Expected result of the procedure.
12. Recording the actions of the tested system.
13. Result of the test procedure.

Test procedure generally consists of five parts. Each part is essential and should be carefully documented.

The Parts of the Test-Procedure Are:

• functional testing steps;
• security testing steps;
• compatibility testing steps;
• load testing steps;
• usability testing steps.

Related Posts:

• How to Document Test Procedure Correctly?[1]
• Duties and Responsibilities Allocation for Test Process. Part I[2]

Source URL: https://blog.qatestlab.com/2013/08/15/what-test-procedure-pattern-should-be-like/

---