Protecting Stomp client against internal failures

Apparently the stomp client is really unhelpful with
failures; this attempts to provide at least a bit
more information.

Signed-off-by: Luke Kanies <luke@madstop.com>

1 files changed, 5 insertions, 0 deletions

diff --git a/spec/unit/util/queue/stomp.rb b/spec/unit/util/queue/stomp.rb
index f2960b3f8..2adf320e1 100755
--- a/spec/unit/util/queue/stomp.rb
+++ b/spec/unit/util/queue/stomp.rb
@@ -45,6 +45,11 @@ describe 'Puppet::Util::Queue::Stomp' do
             lambda { Puppet::Util::Queue::Stomp.new }.should raise_error(ArgumentError)
         end
 
+        it "should fail somewhat helpfully if the Stomp client cannot be created" do
+            Stomp::Client.expects(:new).raises RuntimeError
+            lambda { Puppet::Util::Queue::Stomp.new }.should raise_error(ArgumentError)
+        end
+
         list = %w{user password host port}
         {"user" => "myuser", "password" => "mypass", "host" => "foohost", "port" => 42}.each do |name, value|
             it "should use the #{name} from the queue source as the queueing #{name}" do