Scribd
Upload
59 views2 pages

Dynamic N Static Testing

Static testing involves reviews, inspections, and walkthroughs to verify requirements without executing code. It focuses on correctness and completeness. Dynamic testing executes the application or build to validate requirements through functionality, usability, and performance testing. Static analysis also considers code complexity metrics. White box testing involves code execution and covers all logic paths within functions. Integration testing can test parameter lists and call-call pairs between modules.

Uploaded by

Priyanka Bist
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
59 views2 pages

Dynamic N Static Testing

Static testing involves reviews, inspections, and walkthroughs to verify requirements without executing code. It focuses on correctness and completeness. Dynamic testing executes the application or build to validate requirements through functionality, usability, and performance testing. Static analysis also considers code complexity metrics. White box testing involves code execution and covers all logic paths within functions. Integration testing can test parameter lists and call-call pairs between modules.

Uploaded by

Priyanka Bist
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

In Static Testing we are not going to run the application or build for the correctness and completeness of

requirements. It contains the Testing Methods like Inspections, Walkthroughs, Meetings and Reviews.

Where as in Dynamic Testing we will run the application or build for the validation of requirements. It
contains the Testing Methods like Functionality Testing, Usability Testing and Performance Testing.

Static analysis also involves code complexity metrics, which is very important. In this type
of analysis you can imploy complexity metrics such as Cyclomatic Complexity (gives you an
idea of how maintainable the code is).

What you call Glass Box is also known as White Box testing methods. And these can involve
code execution, which is a dynamic analysis technique. An example is Function/Module Logic
Branch coverage. When you execute the code within the module/function (white box) can all
the logic paths (branches) be reached at least once. There are other types of dynamic
analysis methods that are "white" box.

Integration testing can also be a "white" box type test. You can exercise the parameter lists
of the functions/modules in the compiler. This can be done to exercise intra-functionally
(within the same code module with local functions) and inter-functionally (calls between
different modules with public functions). Also, you can exercise the code to do Call-Called
pair analysis.

Static Testing means: reviews, walkthrough, inspection and


metrics are coming under static testing.

Dynamic Testing means: Unit Testing, Integration Testing,


System Testing, User Acceptance Testing and Exploratory
Testing are coming under dynamic testing.

reviews, walkthrough, inspection, metrics, Unit Testing,


and Integration Testing are coming under White Box Testing.

System Testing, User Acceptance Testing and Exploratory


Testing are coming under Black Box Testing.

Static Testing: Verifying we are developing the Wright


product or not is called static testing or
Verification. or
Have we built the software right (Does it match the
Specification)
Example: analysis of a program carried out with out
executing the program
Static testing will be conducted with help of Reviews and
walk through
Reviews were 4 Types 1) Management Review or split page, 2)
Functional Review 3)formal Review(Ex:Inspection&audit), and
Non Formal Review or Peer Review.
Dynamic testing or Validation Testing: Based on specific
test cases by execution of the test object and running
programs.(Developing the code wright or not)
Have we built the right software? (is this what the
customer wants).
Example: analysis of a program carried out with executing
the program

Dynamic testing carried out by unit, Intigration, System


Testing and User acceptance testing
Whit box testing = unit+Intigration Testing and
Block box testing = System Testing +User acceptance testing
Gray box testing =whit box testing+ Block box testing
(*Gray box testing mostley used only data base testing *)

White box testing is also called Clear box testing, glass


box testing and Structural testing
This test is being carried out by the developer to validate
Developed the code works expected or not is called W.T

W.T is being used in codecavarage which is also done by


programmer Codecavarage is two types 1) stament covarage
and path covarage

Block box testing also called specification base testing

tester has to be test Validate the application is being is


reached according to the customer requirement or not is
called B.T

some of the testing techmiques were interduced in block box


testing

static testing means verification . that means reviews and


meetings conducted to evaluate thecode ,requirements,design
and development.this can be done with check lists,issue
lists, walkthroughs and inspections and meetings.
dynamic testing means validation .after verification
completed it should be conducted.it is exactly testing.it
based on the requirements.

You might also like