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 integrate their prototypes more safely. > > So you're hoping they'll use the stories and get them to pass against > the views as they evolve? > Yeah. I'd like to have them use the stories against the mockups they build, then we move the stories to the live app as we integrate their changes. These are just some initial thoughts I've had, so I'm always open to alternate ideas. One option I thought about was to use pages that don't have any functionality behind them (other than perhaps some basic navigation), then they could design their mockups against these. As we integrate their designs in, we can start adding functionality behind it. This seems more in line with (perhaps one of) the original ideas for stories. > > > I realize that I could use examples for this, but I was hoping to use > > stories. > > There's really no support for this as it stands. Not sure if I'd want > that to change. Other opinions? > > Would it be as simple as supporting render/assigns, like in view specs? In the end, our designer/business have programming skills, so I could have them use example groups; it isn't like example groups are so incredibly cryptic. When you format as specdoc, they provide a decent doumentation; I do like stories better, though. :) -- http://www.coreyhaines.com The Internet's Premiere source of information about Corey Haines
_______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
