What is Integration Testing?
Upon completion of unit testing, integration testing begins. Integration testing is black box testing. The purpose of integration testing is to ensure distinct components of the application still work in accordance to customer requirements. Test cases are developed with the express purpose of exercising the interfaces between the components. This activity is carried out by the test team. Integration testing is considered complete, when actual results and expected results are either in line or differences are explainable/acceptable based on client input.
off the top of my head: • unit testing in the sense of “testing the smallest isolatable unit of an application”; this is typically a method or a class, depending on scale • integration testing • feature testing – this may cut across units, and is the focus of TDD • black-box testing: testing only the public interface with no knowledge of how the thing works • glass-box testing: testing all parts of a thing with full knowledge of how it works • regression testing: test-cases constructed to reproduce bugs, to ensure that they do not reappear later • pointless testing: testing the same basic case more than one way, or testing things so trivial that they really do not need to be tested (like auto-generated getters and setters)
