[EMAIL PROTECTED] wrote:
> It gets included in the Executable Acceptance Test. That's
> one of the nice things about using FIT/FitNesse - since the
> EAT is simply an HTML document, you can include anything
> you want in it. That typically includes enough explanatory text
> to clarify what the tables do, but it can also include links to
> other documents, etc.
Here's a question that's been bothering me: How do you know that the
information captured in the Executable Acceptance Test is a reliable and
complete representation of the story?
Your comment gives a different perspective: If you're saying that you can put
anything you want into the EAT document, that implies you can put the original
stories, use cases, scenarios, or whatever there. If you do this, then of
course the issues about throwing away the originals become moot. Furthermore,
this documentation isn't executable. So while the idea of using the acceptance
tests as the container for the important parts of the early artifacts seems
quite reasonable to me, it also sidesteps the questions that are being raised.
Gary
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
