On 3/17/08, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> [quite a lot]
Okay, I've got it working now. The problem seems to be wrapped up in
the use of transactional fixtures to load the db, and the fact that
fixture teardown actually happens in the SETUP phase, in other words
when you declare a fix
On 3/16/08, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 14, 2008 at 8:12 PM, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> > 2) Having figured that out and moving on, I now have another
> > problem, which is what's the best way to clean up the database so that
> > Scenario A can
On Sun, Mar 16, 2008 at 7:37 AM, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> Okay, right now, I'm not actually using rails stories since I'm
> working through pure business logic sans a UI so there's been no need
> for Rails "integration" testing.
>
> On the other hand I guess it wouldn't hurt t
On 3/16/08, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 14, 2008 at 8:12 PM, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> > I'm trying to use stories to drive some high-level design.
> > ... So far it's been working fairly well,
> > but I've run into a few quirks.
> >
> > 1) I've
On Fri, Mar 14, 2008 at 8:12 PM, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> I'm trying to use stories to drive some high-level design.
>
>
> I've got some branching scenarios where I want to follow a scenario,
> to establish a base situation, and then have different scenarios which
> 'branch' ou
I'm trying to use stories to drive some high-level design.
I've got some branching scenarios where I want to follow a scenario,
to establish a base situation, and then have different scenarios which
'branch' out from that state, possibly several levels deep.
I asked a bit about this a few days a
