Almost Done

One last thing we will do here is clean up some of the dependencies we have introduced. Our package structure has emerged as we were building up the Web service and integrating it with the data access. We have enough code written now to help us see the dependencies between the modules. We will be moving the classes around between assemblies and namespaces to better reflect the emerged architecture. This is an important step of the test-driven development process; we are in fact exposing our architecture by clarifying the packaging boundaries.

We want to be able to distribute our production code without our test code, which necessitates the separation of the service interface tests into a separate assembly just as we did in the previous ...

Get Test-Driven Development in Microsoft® .NET 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.