2006-2007 INT-Evry (Masters IT– Soft Eng) IntegrationTesti ng.1 (OO) Integration Testing What: Integration testing is a phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing. Informally - a (design) point of view Why: The purpose of integration testing is to verify functional, performance and reliability requirements placed on major design artefacts. How: integration testing is a logical extension of unit testing. In its simplest form, two units that have already been tested are combined into a component and the interface between them is tested. But choosing the integration order is non- trivial!
27
Embed
2006-2007INT-Evry (Masters IT– Soft Eng)IntegrationTesting.1 (OO) Integration Testing What: Integration testing is a phase of software testing in which.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
What: Integration testing is a phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing.
Informally - a (design) point of view
Why: The purpose of integration testing is to verify functional, performance and reliability requirements placed on major design artefacts.
How: integration testing is a logical extension of unit testing. In its simplest form, two units that have already been tested are combined into a component and the interface between them is tested. But choosing the integration order is non-trivial!
(OO) Integration vs RegressionTesting – another (incremental development) point of view
Integration tests are performed when new code is added to an existing code base; for example, when a new function is added to a set of existing functions. Integration tests measure whether the new code works -- integrates -- with the existing code; these tests look for data input and output, correct handling of variables, etc.
Regression testing is the counterpart of integration testing: when new code is added to existing code, regression testing verifies that the existing code continues to work correctly, whereas integration testing verifies that the new code works as expected.
Regression testing can describes the process of testing new code to verify that this new code hasn't broken any old code.
Question: is this incremental view a good way of thinking about integration testing or is the design view better?
Component testing •Testing of individual program components•Usually the responsibility of the component developer (except sometimes for critical systems)•Tests are derived from the developer’s experience
Integration testing•Testing of groups of components integrated to create a system or sub-system•The responsibility of an independent testing team•Tests are based on a system specification
• Test the top layer or the controlling subsystem first
• Then combine all the subsystems that are called by the tested subsystems and test the resulting collection of subsystems
• Do this until all subsystems are incorporated into the test
• Special program is needed to do the testing, Test stub :
– A program or a method that simulates the activity of a missing subsystem by answering to the calling sequence of the calling subsystem and returning back fake data.