Static Testing

Is a product testing strategy that is utilized to really take a look at surrenders in programming applications without executing the code. Static testing is finished to stay away from mistakes at the beginning phase of improvement as it is simpler to distinguish the blunders and settle the blunders. It additionally helps find blunders that may not be tracked down by Powerful Testing.  

Its partner is Dynamic Testing which checks an application when the code is run. Read this article for a detailed difference between static and dynamic testing. 

The two main types of static testing techniques are 

  • Manual examinations: Manual examinations include analysis of code done manually, also known as REVIEWS. 
  • Automated analysis using tools: Automated analysis are basically static analysis which is done using tools. 

What is Testing Review? 

A static testing review is a process that involves identifying potential defects in a program. It’s also beneficial for the team to get to know about the project’s progress and come up with effective suggestions. During this process, the documents are thoroughly examined by the team members. 

Reviews can further be classified into four parts: 

  • Informal reviews 
  • Walkthroughs 
  • Technical review 
  • Inspections 

During the Review process four types of participants take part in testing are: 

  • Moderator: Performs entry check, follow up on rework, coaches team member, and schedule the meeting. 
  • Author: Takes responsibility for fixing the defect found and improves the quality of the document 
  • Scribe: It does the logging of the defect during a review and attends the review meeting 
  • Reviewer: Check material for defects and inspects 
  • Manager: Decide on the execution of reviews and ensures the review process objectives are met. 

Types of defects that can be easier to find during static testing are: 

  • Deviations from standards 
  • Non-maintainable code 
  • Design defects 
  • Missing requirements 
  • Inconsistent interface specifications 

Usually, the defect discovered during static testing is due to security vulnerabilities, undeclared variables, boundary violations, syntax violations, inconsistent interface, etc. 

Static testing is performed due to the following reasons: 

  • Early defect detection and correction 
  • Reduced development timescales 
  • Reduced testing cost and time 
  • For improvement of development productivity 
  • To get fewer defects at a later stage of testing 

What are the tests in Static Testing 

In Static Testing, the following things are tested 

  • Unit Test Cases 
  • Business Requirements Document (BRD) 
  • Use Cases 
  • System/Functional Requirements 
  • Prototype 
  • Prototype Specification Document 
  • DB Fields Dictionary Spreadsheet 
  • Test Data 
  • Traceability Matrix Document 
  • User Manual/Training Guides/Documentation 
  • Test Plan Strategy Document/Test Cases 
  • Automation/Performance Test Scripts 

How Static Testing is Performed 

To perform Static Testing, is done in the following ways, 

  • Carry out the inspection process to completely inspect the design of the application 
  • Use a checklist for each document under review to ensure all reviews are covered completely 

The various activities for performing Static Testing are: 

  • Use Cases Necessities Approval: It approves that all the end-client activities are distinguished, as well as any information and result related to them. The more point-by-point and careful the utilization cases are, the more precise and far-reaching the experiments can be. 
  • Utilitarian Prerequisites Approval: It guarantees that the Practical Necessities recognize every single fundamental component. It likewise takes a gander at the information base usefulness, interface postings, equipment, programming, and organization necessities. 
  • Design Audit: All business-level cycles like server areas, network charts, convention definitions, load adjusting, information base openness, test gear, and so forth. 
  • Model/Screen Mockup Approval: This stage incorporates approval of necessities and uses cases. 
  • Field Word reference Approval: Each field in the UI is characterized all around ok to make field-level approval experiments.


Static Testing Techniques 

  • Informal Reviews 
  • Walkthroughs 
  • Technical Reviews 
  • Inspections 
  • Static Analysis 
  • Data Flow 
  • Control Flow 

Tools used for Static Testing 

Various tools used for Static Testing are as follow, 

  • Checkstyle 
  • Soot 
  • SourceMeter