What is Static Testing ?
Static Testing a software testing technique in which the software is tested without executing the code. This happens during the early phase of software development activities.
In other words, we can say that Static testing can be done (manually or with the help of tools) to improve the quality of the application by finding the error at the early stage of development; that is also called the verification process.
1. Types of Reviews
The four (4) common types of reviews are Informal, Walkthrough, Peer Review and Inspection.
|
Informal Review |
During an informal review, the author of the documents presents the documents to the reviewers (or target audience) and receive their comments or feedbacks. |
|
Walkthrough |
This type of review is carried out by an expert in a related subject area. The reviewers will review the documents to confirm the feasibility of the features. |
|
Peer review |
Members of the internal team perform peer review so that every team member reviews the documents to spot any issues. |
|
Inspection |
This involves reviewing the user requirements specifications (URS) and software requirements specifications (SRS) of each individual module or feature to verify the specs listed in the document. |
2. Types of Static Analysis
Static analysis is the process of assessing the code written by programmers to ensure the code meets the required standard. The code will be reviewed to ensure it follows general best practices and adherence to the style guide.In static analysis, the tool will also check for the following flow in the codes:
Data flow: Data flow looks at how data comes into the system, any interactions the data experiences, and how the data leaves the system.
Control flow: Here, we evaluate the order of execution of code statements to ensure it meets the intended behavior.
Why Should We Perform Static Testing?
We can find and address defects and errors during the early phase of software development.
It improves development productivity by anticipating any potential code error, configuration error etc.
It reduces testing costs and shorten the timeline in functional testing.
It can reduce the number of potential defects that could be found later in the process.
We can prevent performance issue and serious security vulnerabilities from the beginning.