We need a reusable utility class for managing temporary directories, so we will extract one from our existing test utilities.
2011-01-28
Let's Code Dimdwarf #32: Application Loading Test Names
Some areas of the system are still only covered by the end-to-end tests, so they need some unit tests to enable testing them faster and to put more design pressure on them. One of these areas is application loading. I begin by choosing the names of the tests to be written, which is easy because I already know based on the existing implementation that what features it has.
2011-01-24
Let's Code Dimdwarf #31: Generics Magic
I did some work off-camera to make the actors and message queues type parameterized, so that a similar bug as was in episode 25 would not happen ever again. In the beginning of this episode I will explain what I did and what kinds of Java generics tricks I was able to use to minimize the boilerplate in the Guice modules. Then it's time to write unit tests for things which are covered only by end-to-end tests.
2011-01-19
RECAP: Let's Code Dimdwarf #21-30
Recap of episodes 21 to 30, at 10 times the normal speed.
P.S. I just got a decent microphone. The sound is now much clearer than what it used to be. Unfortunately it will take until episode 42 for the regular episodes to be recorded with this mic.
2011-01-08
Let's Code Dimdwarf #30: Thoughts on YAGNI
Support for multiple clients has now been implemented. When making this system, initially I made it work on just one client, because I knew that adding features later to a simple codebase is easy and then your understanding of the problem will be better. It took only a bit over 4 hours to add support for more than one client - surely not much longer than if I had built it in already in the beginning.
2011-01-05
Let's Code Dimdwarf #29: Authenticating Multiple Clients
The last thing remaining to support multiple clients is to update the authentication layer.
Subscribe to:
Posts (Atom)