Scribd
Upload
6 views

Static Testing

Uploaded by

200108059
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
6 views

Static Testing

Uploaded by

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

Unit-2

What is Static Testing with Example?

• Static Testing is a software testing method, which is used to check


defects in software application without executing the code.
• Dynamic testing is used to check defects by executing the code. Read
more about Dynamic testing here.
• Static testing refers to a type of test in which no live application is used.
• This type of testing allows you to identify and correct mistakes earlier in
the development process, resulting in fewer problems later on.
• It also aids in the detection and correction of flaws that may not be
discovered by dynamic testing.
• It starts early in the Software Development Life Cycle, therefore it is
completed during the Verification Process.
• In Static Testing, the software application is tested with Review, Walk
Through, Inspection, and Analysis.
• To ensure that the code is correct, developers must adhere to rigorous
testing procedures. This testing aims to find mistakes from the
requirement gathering phase of SDLC (software development life
cycle) all the way through source code.
• Static testing can be used to catch defects in the documentation
phases, which helps to prevent errors at later stages and is therefore
cost-effective.
• Reviews should be used in all significant aspects of software
development, including requirements, design, implementation, testing,
and maintenance.
• Types of defects that are easier to find during static testing are
deviations from standards, missing requirements, design flaws, unused
variables, non-maintainable code, and inconsistent interface
specifications.
Reviews and its Type
Reviews: Reviews are usually performed to identify and correct errors and
uncertainties found in supporting documents such as requirement documents,
design documents, test cases etc.,
Types of Static Testing Reviews
#1. Informal Reviews: Informal reviews do not use any set method to detect
problems. Coworkers review documents and give informal comments.
#2. Walkthrough: The document’s author will explain the document to their
team during a walkthrough. Participants would ask questions, and any notes
are taken down.
#3. Technical Reviews: Peers examine technical specifications in order to
detect any errors.
#4. Inspections: Moderator will do a comprehensive examination as part of
the procedure to detect flaws.
Types of Participants in Review Process
Participants in the review process are as follows
#1. Author: Author’s responsibility is to fix the errors found and
improves the document’s quality.
#2. Moderator: The Moderator is in charge of checking for entries,
following up on reworks, coaching team members and to schedule the
meetings.
#3. Scribe: Logs the error during a review.
#4. Reviewer: Examine the material for defects.
#5. Manager: Determine how evaluations will be carried out and make
sure that the review process goals are achieved.
#2. Static Analysis

Static analysis is where the code developed by developers is evaluated. It is done to find
structural defects that may lead to errors.
Static code analysis can be done both either manually or through automation with the use of
various software testing tools.
Some of the tools which can be used for static analysis of code are:
• Checkstyle
• Clang
• Find Bugs
• JArchitect
• JTest
• Sonarqube
• Soot
• Source meter
• Thread Safe
Types of Static Analysis

#1. Data Flow


In static analysis, the data flow is related to the stream processing.
#2. Control Flow:
Control flow is used to specify how the statements or instructions are
executed.
#3. Cyclomatic Complexity:
It is the measurement of the program’s complexity that is basically
related to the number of independent paths in the control flow graph of
the program.

You might also like