Difference between functional testing and integration testing

Functional Testing :

 

Functional testing is concerned only with the functional requirements of a system or subsystem and covers how well (if at all) the system executes its functions. These include any user commands, data manipulation, searches and business processes, user screens, and integrations.

Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team

Functional testing is when we are testing the software or product as a whole functionality whether it is working properly or not. (Testing button and links)

If you made any changes in any module, we have to verify that whole module is  working as per the functionality or not.

Integration testing :

Integration testing is when you test more than one component and how they functionally working together wiht out any issues. Also verify how the system interacts with your system or the database interacts with your data.

Integration testing tests interfaces between components, interactions to different parts of a system such as an operating system, file system and hardware or interfaces between systems

Test the integrated software only but you test where the data flow is happening and is there any changes happening in the database.

Usually we need fully installed system to perform integration testing. And verify that more componant or module interact each other.

Example:

If we are made changes on Logon page(one module) as per new reqirements. The below testing are

Functinal Testing = verified all the links and buttton on logon page. And give user name and password in logon page and verified its routes to home page successfully or not.

Integration testing = After give user name and password, there is a data flow and also change in database (the login per day increases value by 1).


Remember - clicking links and images is not integration testing. because there is no change in database by just clicking on a link. But while integration testing we are testing data flow (interface between one module to another module)

Types of Integration Testing

1) Top-Down Integration Testing: Top Down Integration as the term suggests, starts always at the top of the program hierarchy and travels towards its branches. This

can be done in either depth-first or breadth-first.

2) Bottom-Up Integration Testing: Bottom –Up integration as it name implies starts at the lowest level in the program structure.

Some Techniques of integration testing: Techniques of integration testing can be given below

1) Top-down testing approach
2) Bottom-up testing approach
3) Big-Bang testing approach
4) Sandwiched testing approach

Conclusion: At last we conclude that Integration testing focuses on testing multiple modules working together.