On 3-apr-2008, at 14:31, David Chelimsky wrote: > On Thu, Apr 3, 2008 at 8:25 AM, Bart Zonneveld > <[EMAIL PROTECTED]> wrote: >> >> >> On 3-apr-2008, at 14:12, Rick DeNatale wrote: >>> On Thu, Apr 3, 2008 at 5:34 AM, Ashley Moran >>> <[EMAIL PROTECTED]> wrote: >>>> On 03/04/2008, joseph <[EMAIL PROTECTED]> wrote: >>>> >>>>> >>>>> Example Story (High level): >>>>> >>>>> Story: Web admin manages pages within the admin system >>>>> Scenario: Add page >>>>> Scenario: edit page. >>>>> Scenario: delete page. >>> >>>> This seems too coarse to me. The controller I'm working on now >>>> will end up >>>> with a corresponding story for each of your scenarios. My >>>> scenarios are >>>> along the lines of "User edits page with valid details", "User >>>> edits page >>>> with missing details", "User edits page and clicks cancel", "User >>>> with >>>> insufficient priveleges tries to delete page" etc. I try to make >>>> a scenario >>>> for each common or complex thing that changes the state of the >>>> system - they >>>> would never fit in one story. >>> >>> On the other hand. Keeping these finer grained scenarios within a >>> single story allows branching using GivenScenario which only works >>> with scenarios within the same story. >> >> I am having the same struggles with the granularity. Is there a good >> "sample" app out there on the interweb? >> Or perhaps someone from the list wants to share their story? :) > > I addressed this in my talk at ETEC last week. Slides are here: > http://www.chariotsolutions.com/slides/pdfs/ete2008- > IntegrationTestingWithRSpec.pdf
Dang. Until The Book comes out, this is probably the best best- practices source for plain text stories with rspec. This should be on the wiki... gr, bartz _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
