Demonstration of using gauntlt with the curl adaptor to check http responses to various methods

gistfile1.sh

Feature: Evaluate responses to various HTTP methods.

  Background:                  # verbs.attack:3
    Given "curl" is installed  # gauntlt-0.1.2/lib/gauntlt/attack_adapters/curl.rb:1
    And the following profile: # gauntlt-0.1.2/lib/gauntlt/attack_adapters/gauntlt.rb:3
      | name     | value      |
      | hostname | google.com |

  Scenario Outline: Verify server responds correctly to various HTTP methods # verbs.attack:9
    When I launch a "curl" attack with:                                      # gauntlt-0.1.2/lib/gauntlt/attack_adapters/curl.rb:5
      """
      curl -i -X <method> <hostname>
      """
    Then the output should contain "<response>"                              # aruba-0.5.3/lib/aruba/cucumber.rb:97

    Examples: 
      | method | response                       |
      | delete | Error 405 (Method Not Allowed) |
      | patch  | Error 405 (Method Not Allowed) |
      | trace  | Error 405 (Method Not Allowed) |
      | track  | Error 405 (Method Not Allowed) |
      | bogus  | Error 405 (Method Not Allowed) |

5 scenarios (5 passed)
20 steps (20 passed)
0m0.593s

verbs.attack

Feature: Evaluate responses to various HTTP methods.

Background:
  Given "curl" is installed
  And the following profile:
    | name     | value      |
    | hostname | google.com |

Scenario Outline: Verify server responds correctly to various HTTP methods
  When I launch a "curl" attack with:
    """
    curl -i -X <method> <hostname>
    """
  Then the output should contain "<response>"
  Examples:
    | method | response                       |
    | delete | Error 405 (Method Not Allowed) |
    | patch  | Error 405 (Method Not Allowed) |
    | trace  | Error 405 (Method Not Allowed) |
    | track  | Error 405 (Method Not Allowed) |
    | bogus  | Error 405 (Method Not Allowed) |