Using TDD: Synchronizing Files with Client / Server

I started learning tdd and wanted to use it in a real project. So I decided to create a simple file synchronization with the client and server in java. After more or less part of the client part, I got stuck while writing the server part.

For unit test logic without access to external resources, I put them in separate classes so that I can make fun of them. So far so good.

Now here is my question:

This image shows how I imagined how everything might look when the green parts are finished and the yellow parts are not yet implemented.

In my case, I would have to go RemoteServera ConnectionManager. To create ClientConnectionHandlerfor, you ConnectionManagerneed a FileAdapterand a Communicator. That sounds like too much to me. Is this normal for tdd'ing, or am I doing something wrong so that everything is checked?

edit: the ClientConnectionHandler class is only responsible for the server-side file synchronization logic, which means: Following my own mini-protocol for receiving files from the client.

+5
source share
1 answer

. , , , . , , - .

IoC , Spring . ( ) .

+2

All Articles