[rspec-users] plain text stories: motivation number 27

Pádraic Brady padraic.brady at yahoo.com
Thu Oct 18 05:44:43 EDT 2007

What Marcus said ++ ;)

I don't think it's a crazy idea, but having workflow both ways would be so much more useful.

Pádraic Brady

OpenID Europe Foundation

----- Original Message ----
From: Marcus Ahnve <marcus at ahnve.com>
To: rspec-users <rspec-users at rubyforge.org>
Sent: Thursday, October 18, 2007 9:45:46 AM
Subject: Re: [rspec-users] plain text stories: motivation number 27

On Wed, Oct 17, 2007 at 09:41:27AM -0500, David Chelimsky wrote:
> This is mostly theoretical, but ...
> I'm starting to use lighthouse (http://llighthouseapp.com) for my
> projects at work. I'm organizing iterations as milestones and stories
> as tickets tagged to a milestone.
> Lighthouse offers an API so that you can write access the data in
> account and write apps to process that data.
> I think you see where this is going.
> It seems to me that a plain text story could be stored in a
> ticket, read in via the lighthouse API ... AND EXECUTED BY STORY
> Call me crazy :)
> Sure, this is theoretical in terms of lighthouse - but it reveals an
> important benefit of plain text stories: it would be possible to
> express stories in any of a variety of systems and have them consumed
> by an adapter that feeds them in to story runner.
> Thoughts?

I think it will be really useful if you start changing issue status
based on the outcome of the run stories. My main beef with issue
trackers has always been just that, that users click a box to say that
something is done instead of it being handled automatically. 

Marcus Ahnve
Blog: http://marcus.ahnve.net
rspec-users mailing list
rspec-users at rubyforge.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/rspec-users/attachments/20071018/0a3dc8dd/attachment.html 

More information about the rspec-users mailing list