Sha256: 4f03e602b702b9d1de669857559925c431e99e2d84198b57043a4d039aa115fe

Contents?: true

Size: 1.37 KB

Versions: 6

Compression:

Stored size: 1.37 KB

Contents

Feature: Scopes
  In order to apply similar behavior to a series of frames
  As a client
  I want to have frame scopes

  Scenario: Applying a set of headers to a series of frames
    Given a 1.1 connection between client and broker
    And a header scope with headers
    | header-name   | header-value |
    | x-my-header   | some value   |
    | canon:unisono | violini      |
    | x-machine     | a\b\c        |
    When the client acks a message by ID "m-1234" and subscription "s-5678" within the scope
    And the client subscribes to "/topic/test" with headers within the scope
    | header-name | header-value      |
    | id          | s-9012            |
    | ack         | client-individual |
    And the frame exchange is completed
    Then the broker should have received an "ACK" frame with headers
    | header-name   | header-value |
    | x-my-header   | some value   |
    | canon:unisono | violini      |
    | x-machine     | a\b\c        |
    | message-id    | m-1234       |
    | subscription  | s-5678       |
    And the broker should have received a "SUBSCRIBE" frame with headers
    | header-name   | header-value      |
    | x-my-header   | some value        |
    | canon:unisono | violini           |
    | x-machine     | a\b\c             |
    | id            | s-9012            |
    | destination   | /topic/test       |
    | ack           | client-individual |

Version data entries

6 entries across 6 versions & 1 rubygems

Version Path
stomper-2.0.6 features/scopes.feature
stomper-2.0.5 features/scopes.feature
stomper-2.0.4 features/scopes.feature
stomper-2.0.3 features/scopes.feature
stomper-2.0.2 features/scopes.feature
stomper-2.0.1 features/scopes.feature