March 2016
Intermediate to advanced
304 pages
8h 9m
English
In chapter 6, you saw various techniques used to mock collaborator classes so that only the class under test affects the outcome of the tests. In some cases, however, you don’t want to mock collaborators but want to test multiple real classes together.
An integration test spans multiple Java classes (instead of just one) and examines the communication among them. Common scenarios that need integration tests are database mappings, security constraints, communication with external systems, and any other cases where testing is focused on a module rather than a single class.
To start, you’ll look at a standalone application powered by a Swing user interface that manages the warehouse ...
Read now
Unlock full access