Feature: Script to ping a queue worker.

@rugged @commands @echo @root-worker @snapshot-worker @targets-worker @test-worker @timestamp-worker
Feature: Script to ping a queue worker.
  In order to test that a worker is running
  As a developer
  I need to receive a ping/echo response.

  Background:
    Given I reset Rugged

  Scenario: The 'echo' Rugged command exists.
    When I try to run "sudo sudo -u rugged rugged echo --help"
    Then I should not get:
      """
      Error: No such command 'echo'.
      """
    And I should get:
      """
      Usage: rugged echo [OPTIONS]
      
        Ping a worker, by sending an echo task on the queue.
      
      Options:
        -m, --message TEXT              The message to send to the worker.
        --worker TEXT                   The specific worker to ping. Can be passed
                                        multiple times.
        -t, --timeout INTEGER           The time to wait for a task to complete (in
                                        seconds).
        --broker-connection-string TEXT
                                        The string used to connect to the broker.
        --help                          Show this message and exit.
      """

  Scenario: Send a ping/echo message, specifying a valid worker.
    When I run the Rugged command "rugged echo --worker=test-worker"
    Then I should get:
      """
      Sending test-worker Ping!...
      Done. Response was: test-worker PONG: Ping!
      """
    Then I should not get:
      """
      debug: Initializing connection to RabbitMQ.
      """
    When I run the Rugged command "rugged logs --local --limit=0"
    Then I should get:
      """
      Sending test-worker Ping!...
      Done. Response was: test-worker PONG: Ping!
      """
    Then I should not get:
      """
      Initializing connection to RabbitMQ.
      """
    When I run the Rugged command "rugged logs --worker=test-worker --limit=0"
    Then I should get:
      """
      test-worker received echo task: Ping!
      """

  Scenario: Send a ping/echo message, specifying an invalid worker.
    When I fail to run the Rugged command "rugged --debug echo --worker=intentionally-invalid"
    Then I should get:
      """
      Sending intentionally-invalid Ping!...
      warning: The operation timed out. Check status of intentionally-invalid.
      """
    When I run the Rugged command "rugged logs --local --limit=0"
    Then I should get:
      """
      Sending intentionally-invalid Ping!...
      Initializing connection to RabbitMQ.
      RuggedTimeoutError: The operation exceeded the given deadline.
      The operation timed out. Check status of intentionally-invalid.
      """
    When I run the Rugged command "rugged logs --worker=test-worker --limit=0"
    Then I should not get:
      """
      test-worker received echo task: Ping!
      """

  Scenario: Send a ping/echo message, specifying the message.
    When I run the Rugged command "rugged echo --worker=test-worker --message=Not-ping"
    Then I should get:
      """
      Sending test-worker Not-ping...
      Done. Response was: test-worker PONG: Not-ping
      """
    Then I should not get:
      """
      debug: Initializing connection to RabbitMQ.
      """
    When I run the Rugged command "rugged logs --local --limit=0"
    Then I should get:
      """
      Sending test-worker Not-ping...
      Done. Response was: test-worker PONG: Not-ping
      """
    Then I should not get:
      """
      Initializing connection to RabbitMQ.
      """
    When I run the Rugged command "rugged logs --worker=test-worker --limit=0"
    Then I should get:
      """
      test-worker received echo task: Not-ping
      """

  Scenario: Send a ping/echo message, specifying multiple workers.
    When I run the Rugged command "rugged echo --worker=test-worker --worker=root-worker"
    Then I should get:
      """
      Sending test-worker Ping!...
      Done. Response was: test-worker PONG: Ping!
      """
    Then I should not get:
      """
      debug: Initializing connection to RabbitMQ.
      """
    When I run the Rugged command "rugged logs --local --limit=0"
    Then I should get:
      """
      Sending test-worker Ping!...
      Done. Response was: test-worker PONG: Ping!
      """
    Then I should not get:
      """
      Initializing connection to RabbitMQ.
      """
    When I run the Rugged command "rugged logs --worker=test-worker --limit=0"
    Then I should get:
      """
      test-worker received echo task: Ping!
      """

  Scenario: Send a basic ping/echo message to all workers.
    When I run the Rugged command "rugged echo"
    Then I should get:
      """
      Sending root-worker Ping!...
      Done. Response was: root-worker PONG: Ping!
      Sending snapshot-worker Ping!...
      Done. Response was: snapshot-worker PONG: Ping!
      Sending targets-worker Ping!...
      Done. Response was: targets-worker PONG: Ping!
      Sending test-worker Ping!...
      Done. Response was: test-worker PONG: Ping!
      Sending timestamp-worker Ping!...
      Done. Response was: timestamp-worker PONG: Ping!
      """
    When I run the Rugged command "rugged logs --local --limit=0"
    Then I should get:
      """
      Sending root-worker Ping!...
      Done. Response was: root-worker PONG: Ping!
      Sending snapshot-worker Ping!...
      Done. Response was: snapshot-worker PONG: Ping!
      Sending targets-worker Ping!...
      Done. Response was: targets-worker PONG: Ping!
      Sending test-worker Ping!...
      Done. Response was: test-worker PONG: Ping!
      Sending timestamp-worker Ping!...
      Done. Response was: timestamp-worker PONG: Ping!
      """
    When I run the Rugged command "rugged logs --limit=0"
    Then I should get:
      """
      root-worker received echo task: Ping!
      snapshot-worker received echo task: Ping!
      targets-worker received echo task: Ping!
      test-worker received echo task: Ping!
      timestamp-worker received echo task: Ping!
      """

6 scenarios (6 passed)
45 steps (45 passed)

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Rugged TUF Server is a trademark of Consensus Enterprises.