In an event-driven system like our Slash framework there comes the time when a feature becomes a bit more complex and the order in which events are triggered is important so the feature works correctly. In this post I’d like to point out how which problems occurred for us during development and how we solved it.
Every now and then there comes a time in a project when it would be nice to be able to write a unit test for a new or already existing feature. The reason could be that the feature is quite complex and we like to make sure to get the basics bug-free before going on creating all the stuff around it. Or you have an existing feature that doesn’t really work the way it should work and it is pretty tedious to find the bug in the running game.