How to Achieve More with Static Testing?
by Nataliia Vasylyna | May 26, 2016 6:51 am
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[1] and automated testing[2] 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.
Learn more from QATestLab
Related Posts:
- manual testing: https://qatestlab.com/services/We-Are-Professionals-in/manual-testing/
- automated testing: https://qatestlab.com/services/We-Are-Professionals-in/automated-testing/
- How to Increase Efficiency of Software Testing?: https://blog.qatestlab.com/2014/09/30/how-to-increase-efficiency-of-a-software-testing-process/
Source URL: https://blog.qatestlab.com/2016/05/26/static-software-testing/