Sha256: 3cca35467063ab4a359097b5df15d8f9163483715bff188f3f8e4602d9addfd9
Contents?: true
Size: 320 Bytes
Versions: 19
Compression:
Stored size: 320 Bytes
Contents
@connectivity Feature: As a developer I want to be able to publish and consume events Scenario: I can publish and consume events Given I am consuming When I publish an event Then I receive that event When I publish an event that cannot be processed by the consumer Then the event remains on the queue
Version data entries
19 entries across 19 versions & 1 rubygems