Static testing:- Static testing is done without executing the code. It is done manually to find errors in the code, requirement documents, test plans, test cases and design documents to find errors in early stage of life cycle. As it is carried out in early life cycle, chances of getting a improved quality and productivity of the product increases by finding errors. It is also called as non- execution or verification testing
Need of Static testing:- As Static testing is carried out at early stage so early feedbacks are provided which helps in getting a product/software with an improved quality and increased productivity. Deviation from requirement, missing requirement, design defects and inconsistent interface specifications are some of the defects which are detected in early life cycle.
Static testing techniques:-
1) Informal Review
2) Technical Review
3) Walkthrough
4) Inspection
1) Informal Review:- Informal Review is carried out by a group of two people in early stage of documentation process which can further involve more people and a meeting. Informal reviews are non documented. In this technique we do not follow any process to find errors in documents and give informal review on it.
2) Technical Review:- It is done by peer review of technical documents like test strategy, test plan and specification requirement documents. It is done to check that documents doesn't contain any discrepancies and is suitable for the project.
3) Walkthrough:- It is not a formal process and is carried by Author who guides the participants through the documents to develop a common understanding and feedback.
4) Inspection:- It is the most formal type of review, led by moderators in which documents are prepared and checked thoroughly by reviewers before meeting. Strict process is followed to find errors in early stages and are documented in a logging list.