Skip to main content

Exact Difference between Static and Dynamic Testing

Difference between Static and Dynamic Testing


            Static Testing
              Dynamic Testing
1
In this type of testing we do not execute the code
In this type of Testing we always execute the code.
2
It means examining and reviewing the software.
It means testing, running, and using the software.
3
In this form of Testing methods like code review, inspection, walkthrough, reviews are used.
In this Testing methods like testing and validations are used.
4
It is done in the phase of verification.
It is done in the phase of validation.
5
This testing means “How we prevent” means it always talks about prevention.
This testing means “How we cure” means it always talks about cure.
6
It is not a time consuming job because its purpose is to examine the software or code.
It is always a time consuming job because its purpose is to execute the software or code and it may also involve running more test cases.
7
As it can always start early in the life cycle it definitely reduces the cost of product or you can say project.
As it not starting early in the life cycle hence it definitely increases the cost of product/project.
8
It is always considered as less cost effective job/task.
It is always considered as more cost effective job/task.
9
It can find errors that dynamic testing cannot find and it is a low level exercise.
It can find errors that static testing cannot find and it is a high level exercise.
10
It is not considered as a time consuming job or task.
It is always considered as a time consuming job or task because it requires several test cases to execute.
11
Techniques/methods of static testing are inspections, reviews, and walkthroughs etc.
Technique/method of dynamic testing is always software testing means testing.
12
Static testing is also known by the name Dry Run Testing.
Dynamic Testing is not known by any other name.
13
It definitely comes before dynamic testing.
It definitely follows after static testing.


Comments

  1. Excellent post and it also comprises a lot of useful facts- Thanks for valuable information. Really enjoyed reading it. Please visit my emc testing page and please leave comments.

    ReplyDelete

Post a Comment

Popular posts from this blog

Difference Between Verification And Validation With Example?

Verification and Validation example is also given just below to this table.                Verification               Validation 1. Verification is a static practice of verifying documents, design, code and program. 1. Validation is a dynamic mechanism of validating and testing the actual product. 2. It does not involve executing the code. 2. It always involves executing the code. 3. It is human based checking of documents and files. 3. It is computer based execution of program. 4.  Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 4.  Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc. 5.  Verification  is to check whether the softwar...

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module. In short you can say regression testing  is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. Regression Testing Example  For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug.  Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of ...

What Is Functional Testing Explain It with Example?

Functional testing means testing the application against business requirements. Functional testing is executed using the functional specifications given by the client or by the design specifications according to use cases given by the design team. Role of functional testing is to validating the behavior of an application. Functional testing is more important because it always verifies that your system is fixed for release. The functional tests define your working system in a useful manner. In functional testing tester has to validate the application to see that all specified requirements of the client whatever we have said in SRS or BRS have been incorporated or not. Functional testing  is always concentrating on customer requirements and whereas the Non-Functional testing is always concentrating on customer expectations. Functional and Non Functional Test Cases Functional test cases target business goals and non functional test cases target performance, resource...