We'll definitely want tagging to suit our needs I think. Really I'm trying
to sound you out on your experience of BA involvement and acceptance of
using SCM etc. I think they're pretty wedded to their tools [word et al]
and it will be hard to move them away from them.

On 23 February 2012 18:00, Brian Repko <[email protected]>wrote:

>
>   I would add that for format - TXT and ODF are supported out of the box
> (as well as Google Docs).
>  What I've found is that I want to tag the stories along with the code so
> that I know these are the tests for this code.
>  That has lead me away from wikis and task tools and to use SCM for
> stories.
>
>  But if you don't see a need for tagging, then yeah, skys the limit.
>
>  b
>
>
>  ----- Original message -----
>  From: "Cristiano Gavião" <[email protected]>
>  To: [email protected]
>  Date: Thu, 23 Feb 2012 14:45:00 -0300
>  Subject: Re: [jbehave-user] managing stories
>  Graham, you can use any approach that fits your company...
>
> I knew about people that are using just txt files saved in SCM
> repositories, or using wiki (as confluence, alfresco) or some task
> management tool (as jira, trac) that can be reached by REST http services,
> or you own document management system.
>
> JBehave can be configured to read the stories from practically all
> possible scenarios...
>
> regards,
>
> Cristiano
>
> On 22/02/12 12:36, Graham Abell wrote:
>
> Hi All,
>
>  Just looking for some insight into how you manage your stories -
> obviously we don't want to end up with a load of word docs as it would seem
> to defeat the purpose of living documentation. I've done some searching but
> I can't see any real advice on what to do instead.
>
>  thanks,
>  graham
>
>
>

Reply via email to