Static and Integration Testing

Static Testing vs Dynamic Testing  To find defects  This testing includes verification process  without executing the code  To find defects  This testing includes validation process  must execute the code vs Static Testing Dynamic Testing

Static testing In Software development, static testing, also called dry run testing, is a form of software testing where the actual program or application is not used. Instead this testing method requires programmers to manually read their own code to find any errors. Static testing is a stage of White Box Testing. Static testing is divided into manual and automated techniques

Walkthrough It is a presentation review in which a review participant narrates a description of the software and the remainder of the review group provides their feedback throughout the presentations.

Code Review A code review is a special kind of inspection in which the team examines a sample of code and fixes any defects in it. In a code review, a defect is a block of code which does not properly implements its requirements, which does not function as the programmer intended or which is not incorrect but could be improved.

Automated Testing Automated Software Testing is the application and implementation of software technology throughout the entire software testing lifecycle with the goal of improving STL efficiency and effectiveness.

Types of Automated Testing  Syntax Parser  Static Verification  Symbolic Execution

Benefits of static testing  Reductions in lifetime costs  Improved communication results  Gaining understand  Aiding in professional development for team members

Integration Testing Integration testing is testing in which a group of components are combined to produce output. It is the phase in software testing in which individual software modules are combined and tested as a group.

Types of integration testing There are four different types of integration testing approach in software testing. Top down Bottom up Sandwich Big Bang

Benefits of integration testing Integration testing finds the bugs that occur when two or more models integrated. Main purpose of Integration testing is to identifying the functional, requirement and performance level bugs.

Presented By:- 4 Jigisha Baria 7 Shruti Chaudhari 9 Heena Choudhary 19 Renu Patel