Chapter 18. Testing

 

This chapter covers
  • Test-driven development in the context of messaging
  • Hamcrest and Mockito matchers for messages
  • Testing asynchronous applications

 

One of the great accomplishments of our industry over the last 20 years is test-driven development (TDD). Where many methodologies have proven only to work in theory or have never proven their need, TDD has flourished. The reason for this is simple: clients only pay willingly for working software, and there’s only one way to prove that software works—test it. In essence, TDD makes the developer responsible for proving that the software works. A green test is the ultimate proof of correctness. If you don’t have a clue how you’re going to test the application, you don’t ...

Get Spring Integration in Action now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial