Ask HN: Better way to write specs?

4 points

11 years ago

Is there a standard way of writing BDD specs in a rule-based format? To me, the traditional Gherkin-style format is too verbose and depends on defining edge-cases in lengthy scenarios.

I'm looking for something that more defines the business logic in English and covers the edge cases in the test code.

Like:

  Feature: Serve coffee
    Rule: If there is no coffee left, refund the money
    Otherwise:
      Rule: Coffee should not be served until paid for and until the button has been pressed
      Rule: If the customer is on the VIP list, don't charge any money

Instead of:

  Feature: Serve coffee
    Coffee should not be served until paid for
    Coffee should not be served until the button has been pressed
    If there is no coffee left then money should be refunded

  Scenario: Buy last coffee
    Given there are 1 coffees left in the machine
    And I have deposited 1$
    When I press the coffee button
    Then I should be served a coffee

  Scenario: VIP buys coffee
    Given there are 1 coffees left in the machine
    And I have deposited 1$
    And I am on the VIP guest list
    When I press the coffee button
    Then I should be served a coffee
    Then my money should be returned

  .. scenario for VIP trying to buy coffee, but no coffee left
  .. scenario for regular user trying to buy coffee, but no coffee left, etc.

(example from: https://github.com/cucumber/cucumber/wiki/Feature-Introduction)

3 comments