recognition.feature

Scenario: Recognise outside of heirachry with line manager recognition approval and reward control table director approval
  Given I am logged in to the system
  And recognition approval is set to manual by line manager
  And reward approval is set to manual with a budget control table of:
    | Director     | 100 |
    | Plus one     | 50  |
    | Line Manager | 1  |
  When I recognise someone outside of my heirarchy for "150"
  Then the recognition status should be pending
  And the reward status should control tabled
  And the line manager should be notified of pending recognition
  And the director should be notified of pending reward
  But no money should be transferred

Guess I'm a little late but I wanted to add my two cents. So I wrote about it: http://blog.rtens.org/tool-tyranny.html

tl;dr - I don't think this discussion is so much about tools as it is about description style and structure. The tools should not dictate a style though. So my approach is to use a tool only for browsing and presentation, not for the specification itself.

@rtens using a parsing adapter could mean more flexibility should the user want to change the structure. But doing so would make it increasingly difficult to match the features to the tests.

So far this style has worked great for us which is why that is the default. I will be focussing on 'Domain Driven Design' in future ramblings, the reason behind styling it this way may then be a little more clear.