Dynamic and Static Testing





Static testing mean check or test the code manually without any execution, here test engineer or TL will check document or requirement, code and design as per prototypes and find the error but he will not execute the code..

So main aim of this type of testing is that improve the quality of software in early stages and save the time. This is also called Verification Testing or Non-execution testing.

Static testing can be done manually or automated, Main thing catch the bugs in the early stages of STLC.

Following word document can be used:
i.                    Specifications of the requirement
ii.                  Document of design or prototypes
iii.                Internal source code
iv.                Test Plan
v.                  Testing Cases
vi.                Test Scripts
vii.              User help document
viii.            Content of web pages

Dynamic Testing:
Opposite to static testing, Developed code will be executed in this testing to perform this testing. Mainly in this testing need to test the software system behavior for functionality, usage of CPU / memory and overall system performance. These all comes in Dynamic Testing.

Motive of Dynamic Testing: To confirm that all requirement provided by client is working properly or not. It is also called Validation Testing or Execution Testing.

Testing – i. Dynamic Testing: a. Functional Testing
b. Non Functional Testing
ii. Static Testing: Review etc.

Techniques of testing which are often used in Static Testing:
i.                    Informal Reviews of Code: In this review tester will not follow any process to find the errors.
ii.                  Technical Reviews: All review process will be followed in a process and all standard will also follow.
iii.                Walkthrough: During code review the developed will sit along with reviewer and provide reviewer expected response.
iv.                Inspection: This is called formal review and follows in strict process to find out the bugs. Reviewers will create a checklist regarding review of developed code and report to related developer to fix found issues.
v.                  Static Code Review: Without executing the source code, review the code systematically. Here Reviewer will confirm the syntax of code, standards of Coding, optimization of code etc. This is also called the white box testing.

Dynamic Testing Techniques:
i.                    Unit Testing: Individual unit or module code will be executed and tested in this testing.
ii.                  Integration testing: Individual units will be integrated together and tested their functionality. This testing confirms that units are working properly with the combination of each other or not.
iii.                System Testing: Finally whole system testing will be performed to confirm the requirement of client.


Difference between the Dynamic and Static Testing:

Difference between the Dynamic and Static Testing
Difference between the Dynamic and Static Testing




No comments:

Post a Comment

Popular Posts