<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><html>On Apr 11, 2008, at 8:15 AM, David Chelimsky wrote:</html><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Apr 11, 2008, at 4:44 AM, Ashley Moran <<a href="mailto:ashley.moran@patchspace.co.uk">ashley.moran@patchspace.co.uk</a>> wrote:<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">On 11 Apr 2008, at 03:14, Rick DeNatale wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">I'm thinking that I might just write a whole new xxx_steps.rb file<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">which would run the same story but at the real user interaction level,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">and keep the model level steps also. I still haven't convinced myself<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">one way or the other.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Wow, I had never thought of this. Could you really write a story that<br></blockquote><blockquote type="cite">could be executed in two different environments based on the steps<br></blockquote><blockquote type="cite">file that got loaded?<br></blockquote><br>Absolutely. That is, in fact, one benefit of plain text stories that we don't have with ruby stories ... Yet.</div></blockquote><div><br></div></div>This is also a motivating factor in my own choice to keep the steps worded at high levels of abstraction. For example:<br><br>Given I am filling in my profile<br>When I enter nothing for E-Mail Address<br>And I submit my info<br>Then I should receive an error message telling me that E-Mail Address is required<br><br>This scenario does not say "page" or "screen." It could run against a web system, desktop, command line, or even a batch system, though that might be a bit of a stretch.<br><br>Of course, there are going to be cases when more granularity is required. If there is a requirement for a very specific user experience, something ajaxy for example, but these should be separated out as UI specific stories.<br><br>Cheers,<br>David<br><div><font class="Apple-style-span" color="#144FAE"><br></font></div></body></html>