Sha256: 4066dda2c3c0a9061fccfac6387be3b35a531ae58d799af44ab6c9ae28340689
Contents?: true
Size: 1.27 KB
Versions: 13
Compression:
Stored size: 1.27 KB
Contents
@all_adapters
Feature: Dynamic Destinations
Sometimes you want to connect to a queue that has some of it's characteristics
determined at runtime. Dynamic destinations allow you to do with without
leaking tons of destination definitions.
Background:
Given I am connected to the broker
Scenario: Sending to a dynamic destination
When I execute the following code
"""ruby
my_new_destination = MessageDriver::Client.dynamic_destination("temp_queue")
my_new_destination.publish("Test Message")
"""
Then I expect to find 1 message on the dynamic destination "temp_queue" with
| body |
| Test Message |
Scenario: Poping messages off a dynamic destination
Given I have a dynamic destination "temp_queue" with the following messages on it
| body |
| Test Message 1 |
| Test Message 2 |
When I execute the following code
"""ruby
my_new_destination = MessageDriver::Client.dynamic_destination("temp_queue")
msg1 = my_new_destination.pop_message
expect(msg1.body).to eq("Test Message 1")
msg2 = my_new_destination.pop_message
expect(msg2.body).to eq("Test Message 2")
msg3 = my_new_destination.pop_message
expect(msg3).to be_nil
"""
Then I expect to have no errors
Version data entries
13 entries across 13 versions & 1 rubygems