Integration Testing

Abstract

The ideal in unit testing is to isolate a single code unit and test it against its behavioural specification. This may involve the construction of extensive “scaffolding” code that allows the tests to proceed. In particular the tester needs to construct: – Driver code to drive the code unit. This is usually contained in the individual JUnit tests. – Stub code to take the place of functions or objects that are used by the code unit in providing functionality. Often the stub code is standing in for as yet unwritten code and the stub has limited functionality using lookup to return a value rather than compute it. Unit test depends on having some kind of specification for the code units. Unit tests often expend effort on testing functionality that is never exercised in the system for which the code module has been constructed.