Book Image

Get Your Hands Dirty on Clean Architecture - Second Edition

By : Tom Hombergs
4 (1)
Book Image

Get Your Hands Dirty on Clean Architecture - Second Edition

4 (1)
By: Tom Hombergs

Overview of this book

Building for maintainability is key to keep development costs low (and developers happy). The second edition of "Get Your Hands Dirty on Clean Architecture" is here to equip you with the essential skills and knowledge to build maintainable software. Building upon the success of the first edition, this comprehensive guide explores the drawbacks of conventional layered architecture and highlights the advantages of domain-centric styles such as Robert C. Martin's Clean Architecture and Alistair Cockburn's Hexagonal Architecture. Then, the book dives into hands-on chapters that show you how to manifest a Hexagonal Architecture in actual code. You'll learn in detail about different mapping strategies between the layers of a Hexagonal Architecture and see how to assemble the architecture elements into an application. The later chapters demonstrate how to enforce architecture boundaries, what shortcuts produce what types of technical debt, and how, sometimes, it is a good idea to willingly take on those debts. By the end of this second edition, you'll be armed with a deep understanding of the Hexagonal Architecture style and be ready to create maintainable web applications that save money and time. Whether you're a seasoned developer or a newcomer to the field, "Get Your Hands Dirty on Clean Architecture" will empower you to take your software architecture skills to new heights and build applications that stand the test of time.
Table of Contents (18 chapters)

Testing a web adapter with integration tests

Moving outward another layer, we arrive at our adapters. Let’s discuss testing a web adapter.

Recall that a web adapter takes input, for example, in the form of JSON strings, via HTTP, might do some validation on it, maps the input to the format a use case expects, and then passes it to that use case. It then maps the result of the use case back to JSON and returns it to the client via an HTTP response.

In the test for a web adapter, we want to make certain that all those steps work as expected:

The preceding test is a standard integration test for a web controller named SendMoneyController, built with the Spring Boot framework. In the testSendMoney() method, we send a mock HTTP request to the web controller to trigger a transaction from one account to another.

With the isOk() method, we then verify that the status of the HTTP response is 200, and we verify that the mocked use case class has been...