Sha256: 8f103b6e4e159b0dc1fdd5494eb8ef5665828d7bd9afb11ba3504d3810b3cb10

Contents?: true

Size: 2 KB

Versions: 26

Compression:

Stored size: 2 KB

Contents

@process
Feature: Flapper command line
  As a systems administrator
  I should be able to manage flapper
  From the command line

  Scenario: Running with --help shows usage information
    When I run `bin/flapper --help`
    Then the exit status should be 0
    And  the output should contain "Usage: flapper"
    And  the output should contain "-b, --bind-ip"

  Scenario: Starting flapper
    When I start flapper with `flapper start --no-daemonize`
    Then flapper should start within 15 seconds

  Scenario: Stopping flapper via SIGINT
    When I start flapper with `flapper start --no-daemonize`
    Then flapper should start within 15 seconds
    When I send a SIGINT to the flapper process
    Then flapper should stop within 15 seconds

  Scenario: Starting, status, and stopping flapper, daemonized
    When I start flapper (daemonised) with `flapper start -d -p tmp/cucumber_cli/flapper_d.pid -l tmp/cucumber_cli/flapper_d.log`
    Then flapper should start within 15 seconds
    When I run `bin/flapper status -p tmp/cucumber_cli/flapper_d.pid`
    Then the exit status should be 0
    And  the output should contain "flapper is running"
    When I stop flapper with `flapper stop -p tmp/cucumber_cli/flapper_d.pid`
    Then flapper should stop within 15 seconds

  Scenario: Starting, restarting and stopping flapper, daemonized
    When I start flapper (daemonised) with `flapper start -d -p tmp/cucumber_cli/flapper_d.pid -l tmp/cucumber_cli/flapper_d.log`
    Then flapper should start within 15 seconds
    When I restart flapper (daemonised) with `flapper restart -d -p tmp/cucumber_cli/flapper_d.pid -l tmp/cucumber_cli/flapper_d.log`
    Then flapper should restart within 15 seconds
    When I stop flapper with `flapper stop -p tmp/cucumber_cli/flapper_d.pid`
    Then flapper should stop within 15 seconds

  Scenario: Getting status when stopped
    When I run `bin/flapper status -p tmp/cucumber_cli/flapper_d.pid`
    Then the exit status should not be 0
    And  the output should contain "flapper is not running"


Version data entries

26 entries across 26 versions & 1 rubygems

Version Path
flapjack-0.9.6 features/cli_flapper.feature
flapjack-0.9.5 features/cli_flapper.feature
flapjack-0.9.4 features/cli_flapper.feature
flapjack-0.9.3 features/cli_flapper.feature
flapjack-0.9.2 features/cli_flapper.feature
flapjack-0.9.1 features/cli_flapper.feature
flapjack-0.9.0 features/cli_flapper.feature
flapjack-0.8.12 features/cli_flapper.feature
flapjack-0.8.11 features/cli_flapper.feature
flapjack-0.8.10 features/cli_flapper.feature
flapjack-0.8.9 features/cli_flapper.feature
flapjack-0.8.8 features/cli_flapper.feature
flapjack-0.8.7 features/cli_flapper.feature
flapjack-0.8.6 features/cli_flapper.feature
flapjack-0.8.5 features/cli_flapper.feature
flapjack-0.8.4 features/cli_flapper.feature
flapjack-0.8.3 features/cli_flapper.feature
flapjack-0.8.2 features/cli_flapper.feature
flapjack-0.8.1 features/cli_flapper.feature
flapjack-0.8.0 features/cli_flapper.feature