Test-driven development (TDD) is one of the best ways to ensure quality of integration development. The idea is to first create automated test cases. The first test round should fail. This failure occurs because the developer has not yet implemented the integration solution that leads to success and ensures that test cases work correctly. 

Developer can start his or her work after the all paths of process execution have been covered with automated test cases. Each test case should turn green to illustrate that the integration solution under construction is coming closer ready status.

When considering TDD in integration development, pay attention to following issues

• TDD requires test automation software compatible with the Integration Platform.
• TDD requires training for designer who is defining the automated test cases and for the developers who uses test automation software.
• TDD is not possible with all Integration Platforms. Therefore, Find out what kind of tools exists. 
• Defining and creating automated test cases adds costs, but radically enhance quality. Because of the costs related issues, management support is essential. Meanwhile, management should consider TDD as an investment to quality.
• Choose a testing tool that allows developer to test without deploying the integration solution. TDD is reasonable only when it is not a huge burden to the developer.
• Beware of process boundaries - originally TDD was developed for unit testing. When external systems are included in test cases, the testing easily overlaps integration’s integration test. Therefore a failing test case may occur due to a failing external test environment. A situation which not common in traditional software TDD.