On Tue, Mar 11, 2008 at 2:53 AM, Corey Haines [EMAIL PROTECTED] wrote:
Hi,
I've been investigating plain text stories, and I had a quick question. How
would I go about creating story tests for views in isolation, instead of the
full stack? I had hoped to be able to do a straight render '/',
On Tue, Mar 11, 2008 at 6:16 AM, David Chelimsky [EMAIL PROTECTED]
wrote:
The reason that I want to do this is that I want to give our
designer/business people a way to write stories to describe their user
interface while they work on the prototype, then give us the stories to
help
us
On Tue, Mar 11, 2008 at 8:03 AM, Corey Haines [EMAIL PROTECTED] wrote:
On Tue, Mar 11, 2008 at 6:16 AM, David Chelimsky [EMAIL PROTECTED]
wrote:
The reason that I want to do this is that I want to give our
designer/business people a way to write stories to describe their user
Corey,
What part of the Story do you like that you want the designers to be
exposed to? A higher level API, the plain text part (separation from
implementation of the test), etc... ?
Zach
On Tue, Mar 11, 2008 at 8:39 AM, Zach Dennis [EMAIL PROTECTED] wrote:
On Tue, Mar 11, 2008 at 8:03 AM,
On Tue, Mar 11, 2008 at 2:39 PM, Zach Dennis [EMAIL PROTECTED] wrote:
+1 for keeping view specs act as view specs and stories act as stories.
Agreed. AFAIK stories are for describing a series of actions and
behavior and that doesn't really fit in nicely with specifying views
in isolation.
Hi,
I've been investigating plain text stories, and I had a quick question. How
would I go about creating story tests for views in isolation, instead of the
full stack? I had hoped to be able to do a straight render '/', but it says
it can't find the method.
The reason that I want to do this is
