Static Testing:

Static type of testing can be performed manually or by a set of tools on the code of an application or program which are not to be executed. It checks the code, requirements and design documents and generates reviews, comments on the work document. With static testing, the intension is to find out the errors, potentially malicious code, code flaws in the software application. It is often called as verification testing as it starts earlier in development life cycle.

Static testing is useful on work documents such as requirement specifications, design documents, source code, test plans, test scripts and test cases, web page content.

Different types of static test techniques are:

• Inspection – It is a formal type of review in which a checklist is prepared to review the work document. The main purpose of inspection is to find defects.
• Walkthrough – In this type of technique a meeting is arranged an dlead by author to describe the product. Attendees can ask questions and a scribe is assigned to make notes.
• Technical reviews – In this type of testing a technical round of review is organized to check whether the code is made according to technical specifications and standards or not. Generally the test plans, test strategy and test scripts are reviewed here.
• Informal reviews – As the name suggests,testing technique where codes are reviewed informally and informal comments are provided is called informal review.

Dynamic Testing:

Dynamic testing is performed in runtime environment where code is in operation mode. When the code as input with a value is being executed,the output of the code is checked and compared with the expected output. Dynamic testing is also known as validation testing as it evaluates the finished product. Dynamic testing is further categorized into two types: Functional testing and Non functional testing.

Different types of dynamic testing are:

• Unit testing – Each unit of the software is tested individually by developers.
• Integration testing – Individually tested modules are the integrated into one based on their functionality.
• System testing – Is performed to check how the modules interact with one another and with the system as a whole.
• Acceptance testing – Is performed at client side to verify if the outcome has met the expected results.