Testing Technique

Static Testing and Dynamic Testing

Static Testing: Static Testing also called Verification. Under this testing technique, code is not executed. In this technique, user just manually code walkthroughs, test documentation review, review the requirement document and design document to find the errors.

Static Testing is more cost effective because this testing is done in the very early phase of software development life cycle so it reduce the cost multiplication to find the errors in early phase. If there is any error in the document then the software will develop same as document . This will increase the cost to fix this issue in later stage so Static Testing is cost effective.


Type of Static Testing:

• Informal Reviews: Informal review is the meeting between 2 person or in later stage people get increase. This meeting is to Author and every time, document need to updated as per quality. The most important thing is that this is non documented meeting. 

• Technical Reviews: In this type of meeting everyone focus on the technical content of the software. In Technical review, defects are found by expert who was focus of the document. The expert may be a Architecture, A Designer or the Key users who work over the document. This Technical review is the defect detection process. It is often performed as a Peer review without management participation.

• Walkthrough: Walkthrough is the process conducted by the Author. This is not a formal process. Author guide the process to all the participant  who taken part in the software by his or her understanding to achieve the common understanding and gather feedback from participant. This process is useful for the persons who are the outside of the software. They can easily understand the process. Walkthrough is useful for high level document like Requirement Specification or Designed Document. 

• Inspection: Inspection is the most formal review process and performed by the trained moderator. The document which is prepared in Inspection , checked by the reviewer before meeting, comparing the work with it's source with using checklist. In this meeting defect found are logged. It involve peer to examine the product.  

This technique is continuous technique and every team member take part in this activity.

In Static Testing team just review the Document/Code/Test Plan and all discussion that team have with the client and as per the review, try to find the errors with discussion and product understanding.

Dynamic Testing: Dynamic Testing also called Validation. Under this testing technique, code is  executed. In this testing we will test the Functional behavior of the Software.

Main focus of this technique to confirm that software should meet as per the Requirement Document. In this technique, code is execute to validate the actual result with the expected result. Dynamic Testing is the part of Black box and White box testing.

Type of Dynamic Testing:

• Unit Testing: This type of Testing comes under white Box Testing and it is performed by the Developer. Unit is the smallest part of the Software . In this testing, Developer verified that the outcome of unit or component or code that he/she written matching with the expected result or not.

• Integration Testing: Integration Testing is next level of Testing after Unit Testing. In this type of Testing the component are combined and then, Tester test them to check the output of combined product and the interaction between the different component. In this type of Testing interaction between software and hardware also tested if hardware and software component have any relation. This comes under both White Box and Black Box Testing.

• System Testing: System Testing is the next level after Integration Testing. In this testing all part of software are combined and tested as per the requirement of the Software. This comes under Black Box Testing.

Dynamic Testing is less cost effective.

In Dynamic Testing, Tester execute the code with input and on produce output, matching the Actual output and Expected output with the Verified Requirement Document and find the errors.