Comment 2 for bug 1098773

Hmmmm. Well if we are going to throw an error, why bother catching & rethrowing at all? Why not just let the existing exceptions bubble up to the test/client?

But, we still need to capture dbusmock's STDOUT and confirm the presents of the method call signatures there. That is the only way to confirm that it is actually calling the correct dbus method. A testsuite that simply says "ok, it didn't throw any errors, it must be working properly then" is not good enough. What if the method is empty, doesn't raise any exceptions, but also doesn't call the correct dbus method? We definitely need to confirm that the dbus methods are being invoked with the correct signature and the only way to do that is by capturing STDOUT from dbusmock and examining it's contents.