Scribd
Upload
2 views

static testing

Testing rm

Uploaded by

osirupee2
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
2 views

static testing

Testing rm

Uploaded by

osirupee2
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Static Testing

Static testing is a verification process used to test the application without implementing the code
of the application. And it is a cost-effective process.

To avoid the errors, we will execute Static testing in the initial stage of development because it is
easier to identify the sources of errors, and it can fix easily.

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.

Important activities while performing static testing:

 Business requirement review


 Design review
 Code walkthroughs
 The test documentation review

Different features we can test in Static Testing?

We can test the various testing activities in Static Testing, which are as follows:

 BRD [Business Requirements Document]


 Functional or system Requirements
 Unit Use Cases
 Prototype
 Prototype Specification Document
 Test Data
 DB Fields Dictionary Spreadsheet
 Documentation/Training Guides/ User Manual
 Test Cases/Test Plan Strategy Document
 Traceability Matrix Document
 Performance Test Scripts/Automation

To perform static testing, we need to follow the below steps:

Step1: To review the design of the application entirely, we will perform the inspection process.

Step2: After that, we will use a checklist for each document under review to make sure that all
reviews are covered completely.
Objectives of Static testing

The main objectives of performing static testing is as below:

 Static testing will decrease the flaws in production.


 Static testing will identify, anticipate and fix the bugs at the earliest possible time.
 It is used to save both time and cost.
 It is used to identify defects in the early stage of SDLC, where we can fix them easily.

Static Testing Techniques

Static testing techniques offer a great way to enhance the quality and efficiency of software
development. The Static testing technique can be done in two ways, which are as follows:

 Review
 Static Analysis

Review

In static testing, the review is a technique or a process implemented to find the possible bugs in
the application. We can easily identify and eliminate faults and defects in the various supporting
documents such as SRS [Software Requirements Specifications] in the review process.

In other words, we can say that a review in Static Testing is that where all the team members
will understand about the project's progress.

In static testing, reviews can be divided into four different parts, which are as follows:

 Informal reviews
 Walkthroughs
 Technical/peer review
 Inspections
 Informal reviews
In informal review, the document designer place the contents in front of viewers, and
everyone gives their view; therefore, bugs are acknowledged in the early stage.
 Walkthrough
Generally, the walkthrough review is used to performed by a skilled person or expert to
verify the bugs. Therefore, there might not be problem in the development or testing
phase.
 Peer review
In Peer review, we can check one another's documents to find and resolve the bugs,
which is generally done in a team.
 Inspection
In review, the inspection is essentially verifying the document by the higher authority,
for example, the verification of SRS [software requirement specifications] document.

Tools used for Static Testing

In static testing, we have several tools in the market, but here we are discussing the most
commonly used tools, which are as follow:

 CheckStyle
 SourceMeter
 Soot

CheckStyle

It is a development tool that is used to help the developers write Java code, which follows a
coding standard. The CheckStyle tool automates the process of checking Java code.
It is a highly configured tool, which is made to support almost any coding standard. The Google
Java Style, Sun code conventions are those configuration files, which is supported by
CheckStyle.

Feature of CheckStyle

Following are the most common features of CheckStyle:

 It can check various characteristics of our source code.


 The CheckStyle code has the capability to verify the code layout and formatting issues.
 It can also help to identify the method design problems, class design problems.

SourceMeter

It is an advanced tool for the specific static source code analysis of various programming
languages such as C, C++, C#, Java, Python, and RPG projects.

With the SourceMeter tool's help, we can easily identify the vulnerable spots of a system under
development from the source code.

The free version with partial functionality of SourceMeter can be accessible for all programming
languages.

In SourceMeter, we can use the output of the analysis, the quality of the analyzed source code to
enhance and developed both the short and long term in a directed way.

Feature of SourceMeter

The most commonly used features of the SourceMeter tool are as follows:

 It provides the most precise coding error detection.


 The SourceMeter tool will provide a deep static code analysis.
 It improved the user interface with the help of third-party integration.
 It will provide platform-independent command-line tools.

Soot
It is a Java optimization framework, which means that it is a framework for analyzing and
transforming Java and Android applications where we can test the following aspects:

 Named module and modular jar files.


 Automatic modules, which means the modules are repeatedly created from jars in the module-
path.
 Exploded modules
 Resolving modules in Soot's

And a Soot can also produce possibly transformed code in the various output formats such as Android
bytecode, Java bytecode Jasmin, and Jimple.

Advantages of Static Testing

The advantages of static testing are as follows:

 Improved Product quality


Static testing will enhance the product quality because it identifies the flaws or bugs in the initial
stage of software development.
 Improved the efficiency of Dynamic testing
The usage of Static testing will improve Dynamic Testing efficiency because the code gets
cleaner and better after executing Static Testing.
As we understood above, static Testing needs some efforts and time to generate and keep good
quality test cases.
 Reduced SDLC cost
The Static Testing reduced the SDLC cost because it identifies the bugs in the earlier stages of
the software development life cycle. So, it needs less hard work and time to change the product
and fix them.
 Immediate evaluation & feedback
The static testing provides us immediate evaluation and feedback of the software during each
phase while developing the software product.
 Exact location of bug is traced
When we perform the static testing, we can easily identify the bugs' exact location compared to
the dynamic Testing.

You might also like