I have been working on a msg4r wrapper that provides a number of
messaging clients (i.e. Websphere MQ, ActiveMQ, Stomp) to ruby all
with that same API. I have some simple unit tests in place that
require the actual messaging systems to be available - this mean that
there is significant work required to setup the test, but when they
run I know that they are actually working. I am considering some sort
of mock approach, but I fear that I will be missing out on testing the
specifics of the wire protocols, timing etc.
I am not sure if there is a “right” answer, but I was wondering if
there were any ideas/hints other developers might have.