Scribd
Upload
177 views

Static Testing Vs Dynamics Testing

Static testing involves manually or automatically reviewing documents like requirements, design, and source code without executing the code. This helps find errors early. Dynamic testing executes the code and checks functionality, performance, and validation against requirements. Static testing verifies documents while dynamic testing validates the software works as intended. Both are important to catch defects at different stages of development.

Uploaded by

Jhanvi Pathak
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
177 views

Static Testing Vs Dynamics Testing

Static testing involves manually or automatically reviewing documents like requirements, design, and source code without executing the code. This helps find errors early. Dynamic testing executes the code and checks functionality, performance, and validation against requirements. Static testing verifies documents while dynamic testing validates the software works as intended. Both are important to catch defects at different stages of development.

Uploaded by

Jhanvi Pathak
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

What is Static Testing?

Static Testing is a type of software testing in which software application is


tested without code execution. Manual or automated reviews of code,
requirement documents and document design are done in order to find the
errors. The main objective of static testing is to improve the quality of
software applications by finding errors in early stages of software
development process.

Static testing involves manual or automated reviews of the documents. This


review is done during an initial phase of testing to catch Defect early in
STLC. It examines work documents and provides review comments. It is
also called Non-execution testing or verification testing.

Examples of Work documents-

 Requirement specifications
 Design document
 Source Code
 Test Plans
 Test Cases
 Test Scripts
 Help or User document
 Web Page content           

What is Dynamic Testing?


Under Dynamic Testing, a code is executed. It checks for functional
behavior of software system, memory/cpu usage and overall performance
of the system. Hence the name "Dynamic"

The main objective of this testing is to confirm that the software product
works in conformance with the business requirements. This testing is also
called an Execution technique or validation testing.

Dynamic testing executes the software and validates the output with the
expected outcome. Dynamic testing is performed at all levels of testing and
it can be either black or white box testing.

KEY DIFFERENCE
 Static testing was done without executing the program whereas
Dynamic testing is done by executing the program.
 Static testing checks the code, requirement documents, and design
documents to find errors whereas Dynamic testing checks the
functional behavior of software system, memory/CPU usage and
overall performance of the system.
 Static testing is about the prevention of defects whereas Dynamic
testing is about finding and fixing the defects.
 Static testing does the verification process while Dynamic testing
does the validation process.
 Static testing is performed before compilation whereas Dynamic
testing is performed after compilation.
 Static testing techniques are structural and statement coverage while
Dynamic testing techniques are Boundary Value Analysis &
Equivalence Partitioning.

Static Testing Techniques:


 Informal Reviews: This is one of the type of review which doesn't
follow any process to find errors in the document. Under this
technique, you just review the document and give informal comments
on it.
 Technical Reviews: A team consisting of your peers,   review the
technical specification of the software product and checks whether it
is suitable for the project. They try to find any discrepancies in the
specifications and standards followed. This review concentrates
mainly on the technical documentation related to the software such
as Test Strategy, Test Plan and requirement specification
documents.
 Walkthrough: The author of the work product explains the product to
his team. Participants can ask questions if any.  A meeting is led by
the author. Scribe makes note of review comments
 Inspection: The main purpose is to find defects and meeting is led
by a trained moderator. This review is a formal type of review where
it follows a strict process to find the defects. Reviewers have a
checklist to review the work products.They record the defect and
inform the participants to rectify those errors.
 Static code Review: This is a systematic review of the software
source code without executing the code. It checks the syntax of the
code, coding standards, code optimization, etc. This is also termed
as white box testing.This review can be done at any point during
development.

Dynamic Testing Techniques:

 Unit Testing: Under Unit Testing, individual units or modules are


tested by the developers. It involves testing of source code by
developers.
 Integration Testing: Individual modules are grouped together and
tested by the developers. The purpose is to determine what modules
are working as expected once they are integrated.
 System Testing: System Testing is performed on the whole system
by checking whether the system or application meets the requirement
specification document.

Also, Non-functional testing like performance, Security Testing fall under


the category of dynamic testing.

Difference between Static and Dynamic Testing:

Static Testing Dynamic Testing


Testing was done without executing the Testing is done by executing the program
program

This testing does the verification process Dynamic testing does the validation process

Static testing is about prevention of Dynamic testing is about finding and fixing
defects the defects

Static testing gives an assessment of code Dynamic testing gives bugs/bottlenecks in the
and documentation software system.

Static testing involves a checklist and Dynamic testing involves test cases for
process to be followed execution

This testing can be performed before Dynamic testing is performed after


compilation compilation

Static testing covers the structural and Dynamic testing techniques are Boundary
statement coverage testing Value Analysis & Equivalence Partitioning.

Cost of finding defects and fixing is less Cost of finding and fixing defects is high

Return on investment will be high as this Return on investment will be low as this
process involved at an early stage process involves after the development phase

More reviews  comments are highly More defects are highly recommended for
recommended for good quality good quality.

Requires loads of meetings Comparatively requires lesser meetings

You might also like