<div class="gmail_quote">On Thu, Apr 10, 2008 at 8:46 PM, Tim Haines <<a href="mailto:tmhaines@gmail.com">tmhaines@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br><br>I'm a little unhappy with how my stories are organised, and am wondering if anyone has found any particular method nicest. I'm working within an admin namespace, and currently have a plain text story file for each controller in the admin folder. I also have a steps subfolder, with one step file per controller.<br>
<br>I'm thinking it would be nicer to add a little more granularity here, and to break the plain text story files down further into "actions" on each controller so there's fewer stories per story file. This could be done either in the one folder, or by adding a bunch of subfolders.<br>
<br>I figure this is pretty common though, and that there will be one or two approaches that have evolved to work pretty well?<br></blockquote><div><br></div><div>I organize my stories based on related behavior usually as defined by the customer. For example:</div>
<div><br></div><div> - stories/</div><div> - projects/</div><div> - a_user_creating_a_project_story</div><div> - a_project_manager_adding_users_to_a_project_story</div><div> - admin/</div><div> - an_admin_removing_users_story</div>
<div><br></div><div>I use stories as system level integration tests, so they usually cover a broader scope than a controller/action.</div><div> </div></div>-- <br>Zach Dennis<br><a href="http://www.continuousthinking.com">http://www.continuousthinking.com</a>