In many of the projects that I have worked on, the application we’re building needs to integrate with a back-end system or a web service layer that is maintained by a third party or by another team. In these cases, we shouldn’t assume we’ll have the ability to ensure that the other group has set up an automated test bed to verify regression. Especially if that other system is having changes made to it to support the project!
This is where integration testing comes into play. There are a few things that you should be doing with your unit tests to ensure your integrations continue working throughout the lifetime of your project, and also that your automated tests are running efficiently so that your team is not slowed down waiting on expensive integration unit tests that are running for long periods of time.
View original post 810 more words