Sha256: d5b1fb5dd02c1ec06f7bb909f1f4407c5d426619da866d213bf8e49510d9d9c4

Contents?: true

Size: 427 Bytes

Versions: 11

Compression:

Stored size: 427 Bytes

Contents

@all_adapters
Feature: Logging

  You can configure the logger by setting it on `MessageDriver.logger`.
  If you don't provide a logger, then an info level logger will be created
  and sent to `STDOUT`.

  Scenario: Starting the broker
    Given I am logging to a log file at the debug level
    And I am connected to the broker

    Then the log file should contain:
    """
    MessageDriver configured successfully!
    """

Version data entries

11 entries across 11 versions & 1 rubygems

Version Path
message-driver-1.0.1 features/logging.feature
message-driver-1.0.0 features/logging.feature
message-driver-0.7.2 features/logging.feature
message-driver-0.7.1 features/logging.feature
message-driver-0.7.0 features/logging.feature
message-driver-0.6.1 features/logging.feature
message-driver-0.6.0 features/logging.feature
message-driver-0.5.3 features/logging.feature
message-driver-0.5.2 features/logging.feature
message-driver-0.5.1 features/logging.feature
message-driver-0.5.0 features/logging.feature