How to Achieve More with Static Testing?

May 26 06:51 2016 by Nataliia Vasylyna Print This Article

Unlike dynamic testing, static testing is performed without execution of software development artifacts such as code, requirements or design.

In a software testing company, static testing rarely gains considerable attention even though it is a part of independent validation & verification of a product. Static testing implies inspections, reviews, searching for violations of coding standards, etc.

If a software tester does not have much experience in static testing, the best advice for him/her will be to thoroughly plan this activity and apply the principles of dynamic testing.

What Should Be Included into Static Test Plan?

List of documents to be reviewed
Methods used for reviewing the documentation
Review type needed for each document
Criteria based on which a document can be considered as approved
Step-by-step description of the reviewing procedure
List of required tools
Division of responsibilities among different project participants such as approvers and document owners
List of employees assigned on different reviews
Schedule and deadline for static testing

Testers should spare no effort in executing static testing. They can use the experience gathered during manual testing and automated testing to find any design defects, flaws in code and poorly-written specifications. This way, static testing will become one of the aspects that help to deliver software testing services of a high quality.