Sha256: 12d04fdfc071b927b23d6c4cfe0468e2c8359b1c1512a81c1e5424fa335ef81f

Contents?: true

Size: 1.31 KB

Versions: 1

Compression:

Stored size: 1.31 KB

Contents

Feature: Send and message
  In order exchange information
  As a client
  I want to be able to transmit SEND and receive MESSAGE frames
  
  Scenario Outline: sending and receiving messages with content-types
    Given a 1.1 connection between client and broker
    And the client subscribes to <destination>
    When the client sends a <content-type> <body> to <destination>
    And the frame exchange is completed
    Then the client should have received a <content-type> message of <body>
    
    Examples:
      | destination  | content-type      | body          |
      | /queue/test1 | "text/plain"      | "hello world" |
      | /queue/test2 | "application/xml" | "<xml></xml>" |

  Scenario Outline: sending and receiving messages with encodings
    Given a 1.1 connection between client and broker
    And the client subscribes to <destination>
    When the client sends a <body> encoded as <encoding> to <destination>
    And the frame exchange is completed
    Then the client should have received a <content-type> message of <body> encoded as <final encoding>

    Examples:
      | destination  | content-type | body          | encoding     | final encoding |
      | /queue/test1 | "text/plain" | "hello world" | "UTF-8"      | "UTF-8"        |
      | /queue/test2 | ""           | "hello world" | "ASCII-8BIT" | "ASCII-8BIT"   |

Version data entries

1 entries across 1 versions & 1 rubygems

Version Path
stomper-2.0.0 features/send_and_message.feature