LA LA LA Testing Testing

In a previous post I got a little carried away with all the great testing results, but that ran into an expected wall.

Unit and integration tests are meant to validate your architecture and code and expose gaps. Well we discovered a few gaps and it took us a minute to refactor the parser, language, and then the text service, which included adding a new package 'if-services'.

With all of that settled, we're back to testing.

We had to run back through core, world-model, lang-en-us, and if-domain before continuing on to stdlib which has all of the action handlers.

And I had forgotten we had only started testing stdlib and basically needed to start over with a new testing template. Then Claude quietly implemented the wrong test pattern for the actions and we had to redo every set of tests for every action. Then we found remnants of the bad testing and to go through everything a third time and this led to some actual design issues, which are now resolved.

The main issue was we have RoomTrait, ActorTrait, and ContainerTrait. Do we create a dependency that RoomTrait always also auto-adds ContainerTrait?

No. We're just forcing the assumption that RoomTrait and ActorTrait are automatically containers without the ContainerTrait.

I love it when we get into design issues. That's the fun part of all of this.