Learn how Static testing is useful
Posted By : Tanisha Sharma | 31-Aug-2019
Particular types of static software testing involve code analysis, inspection, code reviews, and walkthroughs. Can you visualize detecting defects without managing the actual testing i.e. either manual or automation testing on just developed software product, So there is testing which is called as Static testing from this we can test the software without literally executing the code, the static testing technique has the following two basic notions:
I) Review of Supporting Project Documents:
This technique includes the procedure to grab and detach errors, sacking or ambivalence in the different supporting documents such as software requirements specification (SRS), a document of technical design, a document of business requirement, document of functional requirement, document of test cases.
II) Static Analysis:
This technique includes the assessment of the code standard written by developers. There are various tools such as PMD, Sonar Cube, etc. which can examine the code and differentiate it with the quality practices, analyzing the unused variables, dead code, infinite loop, etc. It assists to recognize the structural defects rapidly which may later result in actual software defects.
1) Informal Review:
It is a type of evaluation where confirmation is given by the writer of form such as software requirements specification (SRS), a document of test cases, design document, a document of business requirement, a document of functional requirements.
Documents walkthrough is basically done with the specialist or the senior person of the team. For example, Software Requirements Specification Document (SRS) will be evaluated with the Business leads who have given the requirements, Functional Requirements Document (FRD) will be evaluated with the technical team who is going to write the solution, test cases document will be evaluated by the testing team who is going to accomplish those test, etc.
3) Peer Review:
It is the review with the peer to fortify maker and checker. A group of two or more can analyze each other work to outline the usual mistake such as spelling mistake, workflow mistake, requirement assembled helps in scheduling mistake, etc.
It is the technique to ratify the documentation work by the devoted governance team.