Static Testing Strategies

Static  Testing  Strategies: 

Static testing is performed in the early stage of development to avoid errors as it is easier to find sources of failures and it can be fixed easily. The errors that can’t not be found using Dynamic Testing, can be easily found by Static Testing.

 

Review:

This technique involves the method to catch and remove errors, redundancy or ambiguities in the different supporting documents 

1. Informal Review: This is a kind of review where presentation is given by the creator of documents such as software requirements specification (SRS), technical design document (TDD), business requirements document (BRD), functional requirement documents (FRD), test cases document, etc. to the wide audience.
2. Walkthrough: Documents walkthrough is usually done with the expert or the senior member of the team. For example, Software Requirements Specification Document (SRS) will be reviewed with the Business lead who have provided the requirements, Functional Requirements Document (FRD) will be reviewed with the technical team who is going to write the solution, test cases document will be reviewed by the testing team who is going to execute those test, etc.
3. Inspection: It is the technique to validate the documentation work by the dedicated governance team. For example, the BRD (Business Requirement Document), TDD (technical design Document), change ticket, etc. are reviewed by compliance, tollgate team, and change governance respectively
4. Peer Review:It is the review with the peer to ensure maker and checker. A team of two or more can review each other's work to outline common mistakes such as spelling mistakes, workflow mistakes, requirement gathering, scheduling mistakes, etc.