<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Unless you're looking for the steps to show up when you run things, why not just have a helper method that does the setup for you and then have a Given step that invokes that method?<div class="Ih2E3d">
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I know I can extract logic into steps, but I'd like the pre-requisite scenarios to have some assertions, and it doesn't feel right to put assertions in steps (if that's possible).<br>
</blockquote>
<br></div>
I'm not sure understand this. Don't you have expectations (assertions) in all your Then steps?<br>
</blockquote></div><br>Sure. I was just hoping I could keep my prereq stuff as a story in its own right - more for clarity when discussing requirements than for any other reason. If it's just a step or a helper method, then that particular story is reduced to a one-liner. I know I could always do both, and not be 100% DRY, so I guess that's what I'll do.<br>
<br>Thanks for the advice<br><br>David<br><br><br>