Comments on: Imperative vs Declarative Scenarios in User Stories http://www.benmabey.com/2008/05/19/imperative-vs-declarative-scenarios-in-user-stories/ [ software_engineering, ruby, rants, randomness ] Tue, 06 Jan 2009 10:56:46 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Ben Mabey http://www.benmabey.com/2008/05/19/imperative-vs-declarative-scenarios-in-user-stories/comment-page-1/#comment-1284 Ben Mabey Mon, 01 Dec 2008 17:17:22 +0000 http://www.benmabey.com/?p=19#comment-1284 Adam, your right on. A lot of my stories (cucumber features) now have both styles mixed. I think the "right" mix of the two is different per project and even per problem. Adam, your right on. A lot of my stories (cucumber features) now have both styles mixed. I think the “right” mix of the two is different per project and even per problem.

]]> By: Adam http://www.benmabey.com/2008/05/19/imperative-vs-declarative-scenarios-in-user-stories/comment-page-1/#comment-1283 Adam Mon, 01 Dec 2008 05:23:01 +0000 http://www.benmabey.com/?p=19#comment-1283 I know that you mentioned both declarative and imperative are useful in their own contexts, but I just want to add that the best products tend to focus on both types of use-cases. In other words, it is always the little things that make a product great and set it apart from all the other functionally comparable products. Of course, this is usually the client's prerogative, not the developers. Thanks for the great post! I know that you mentioned both declarative and imperative are useful in their own contexts, but I just want to add that the best products tend to focus on both types of use-cases. In other words, it is always the little things that make a product great and set it apart from all the other functionally comparable products. Of course, this is usually the client’s prerogative, not the developers. Thanks for the great post!

]]> By: Ben Mabey http://www.benmabey.com/2008/05/19/imperative-vs-declarative-scenarios-in-user-stories/comment-page-1/#comment-265 Ben Mabey Thu, 22 May 2008 03:34:32 +0000 http://www.benmabey.com/?p=19#comment-265 Very true. In the end the declarative approach gives you a lot more flexibility because you can swap out your matchers... So you could have a set that uses webrat or a set that uses selenium, or one that uses the objects directly, etc... Very true. In the end the declarative approach gives you a lot more flexibility because you can swap out your matchers… So you could have a set that uses webrat or a set that uses selenium, or one that uses the objects directly, etc…

]]> By: Gwyn Morfey http://www.benmabey.com/2008/05/19/imperative-vs-declarative-scenarios-in-user-stories/comment-page-1/#comment-256 Gwyn Morfey Wed, 21 May 2008 10:40:55 +0000 http://www.benmabey.com/?p=19#comment-256 We hit this recently. Imperative tests feel a lot like view testing to us, which is why we're trying to avoid it. Declarative tests look perfect. Since our design team often lags behind the developers, this helps us to avoid rewriting the stories (although we'll have to change the step matchers) once the design is ready. We hit this recently. Imperative tests feel a lot like view testing to us, which is why we’re trying to avoid it. Declarative tests look perfect.

Since our design team often lags behind the developers, this helps us to avoid rewriting the stories (although we’ll have to change the step matchers) once the design is ready.

]]>