Writing cukes describing the real business value a feature is providing is hard. We end up having an horrendous amount of step definitions that muddle the real value the feature is providing; cluttered with interactions with the UI. This talk describes a different approach to writing cukes following a pattern that has evolved from working on several customer projects, The Impersonator Pattern. With this approach to defining your step definitions you will have clearer steps in your cukes. You will be able to see in "one go" what a certain type of user can do in the application you are describing and benefit from the clarity of the cukes.

No outline is available