Integration testing is used to test interaction between different components (or units) or between different parts of the system, for example operating system, hardware, file system or interaction between different systems. It means that if for example you have two features being developed separately and they will interact with each other when implemented, integration testing will be to verify that they operate correctly together.
It can be done by either specified integration tester or a testing team highly experienced in this type of testing and aware its pitfalls and dark corners so it could provide a great integration testing service and ensure your system is stable as a rock, which DeviQA`s teams are more than capable of.When modules are tested separately, they perform as per requirement but when they are integrated, functional, requirement and performance related issues may occur due to the integration. That is why integration testing is a total must and the bigger your app is the more important it will get.
Depending on your requirements and need you may consider different integration testing approaches, each one with its benefits.
Bottom up. This is a logical follow-up for a unit testing. All low level modules, procedures and functions are compiled and tested together and then serve as a base for testing of the next, higher level modules interaction. It's useful if all (preferably) or almost all same-level modules are ready. Also by results of such tests it's easy to see the readiness level of the system.Top down. The total opposite of the first one. All top-level components are tested first and then lower-level modules are being added one by one until the system is complete and its parts seamlessly interact with each other. During testing some low-level components may be simulated by plugs with alike functionality until they are replaced with a fully developed active component“Big Bang” Integration. For example most of your system`s different level and priority components are ready, you gather them all together to form a complete system and then you test them - this will be Big Bang integration testing. This is a great approach if you need to save some time and your testing team in good enough to not mix things, because if testing results, progress and cases are not tracked and properly recorded you will get an unreliable result which may cause time and financial losses.
COPYRIGHT DEVIQA SOLUTIONS 2018. ALL RIGHTS RESERVED.