> Jay - are you familiar with Acceptance Test Driven
> Development/Planning and/or Test Driven Development?
I am with TDD and Acceptance testing (not sure if this is the same as
Acceptance Test Driven Development) . I use a more classic approach to use
Martin Fowler's terminology which is why I
On Jan 12, 2008 8:35 PM, Jay Donnell <[EMAIL PROTECTED]> wrote:
> >because if you have integration tests covering everything,
> >then you'll know pretty quickly when your tests aren't up to par.
>
> If we have integration tests that cover everything then why have another set
> of tests? At that po
>because if you have integration tests covering everything,
>then you'll know pretty quickly when your tests aren't up to par.
If we have integration tests that cover everything then why have another set of
tests? At that point wouldn't it simply be duplication and wouldn't it create
more work
http://synthesis.rubyforge.org/ *just* showed up in my feedreader
(well, the links at the bottom did)
On Jan 11, 2008 9:28 PM, Jay Donnell <[EMAIL PROTECTED]> wrote:
>
> > If you were to rename deposit to credit, and withdraw to debit
>
> I'm more concerned with adding a parameter or changing the
On Jan 12, 2008, at 3:33 PM, Ben Mabey wrote:
> Jay Donnell wrote:
>>
>> Does anyone know of any open source ruby apps (preferably rails)
>> that use good BDD so I can see how it's done right rather than ask
>> a bunch of questions?
>>
>>
>>
>>
>
> Hmm.. I don't know of any rails apps that ar
Jay Donnell wrote:
>
> Does anyone know of any open source ruby apps (preferably rails) that use
> good BDD so I can see how it's done right rather than ask a bunch of
> questions?
>
>
>
>
Hmm.. I don't know of any rails apps that are open source that you could
look at.. But I know datamappe
> If you were to rename deposit to credit, and withdraw to debit
I'm more concerned with adding a parameter or changing the default value of a
parameter. My fear is that given enough time and size there will be a fair
number of inconsistent mocks or mocks that aren't doing any real testing. It
On Jan 11, 2008 5:11 PM, Jay Donnell <[EMAIL PROTECTED]> wrote:
> >> The thing is that, ideally, you don't want to have to make changes to
> >> the tests for object A when you're refactoring B.
> >>
> >> WDYT?
>
> > Yeah, I buy that. Not everyone does though. Or at least not everyone
> > feels th
>> The thing is that, ideally, you don't want to have to make changes to
>> the tests for object A when you're refactoring B.
>>
>> WDYT?
> Yeah, I buy that. Not everyone does though. Or at least not everyone
> feels that it's a particularly important goal.
I think the fear many of us classicis
On Jan 11, 2008 1:48 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Jan 11, 2008 3:43 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> > I don't have any problem with that. I do things that way, and I get
> > my work done just fine. However, I'm having a tough time clarifying
> > my position when
On Jan 11, 2008 3:43 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> I'm going to hijack this a bit :)
>
> On Jan 11, 2008 1:25 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> >
> > But the target of stories are system level descriptions of behaviour.
> > This will inevitably appear to have some overl
I'm going to hijack this a bit :)
On Jan 11, 2008 1:25 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
>
> But the target of stories are system level descriptions of behaviour.
> This will inevitably appear to have some overlap with the specs for
> the outermost layers of the system. But when you s
On Jan 11, 2008 3:16 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> A couple months ago I asked how stories and specs might impact each
> other. [1]If you look at Dan North's example of what's in a story
> [2], and you imagine using the spec framework to drive the design, you
> can probably imagin
A couple months ago I asked how stories and specs might impact each
other. [1]If you look at Dan North's example of what's in a story
[2], and you imagine using the spec framework to drive the design, you
can probably imagine a significant bit of overlap in the two. Is that
a bad thing? I'm n
On Nov 14, 2007 5:50 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> On Nov 13, 2007 4:00 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> > On Nov 13, 2007 5:17 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> > > Let's say in some banking software we have a transfer screen, and
> > > there are three possi
On Nov 13, 2007 4:00 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Nov 13, 2007 5:17 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> > Let's say in some banking software we have a transfer screen, and
> > there are three possible errors: insufficient funds, source account
> > frozen, target acco
On Nov 13, 2007 5:17 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> On Nov 13, 2007 11:51 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> > Keep in mind that that goes nearly unnoticed in java or .NET because
> > of the refactoring tools available on those platforms. Change a method
> > name once
On Nov 13, 2007 11:51 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Nov 13, 2007 1:10 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> > I've been thinking about the role that stories played compared to
> > specs, and that "should we use should" thread brought those thoughts
> > up again.
> >
> >
On Nov 13, 2007 1:10 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> I've been thinking about the role that stories played compared to
> specs, and that "should we use should" thread brought those thoughts
> up again.
>
> First I want to discuss whether or not specs are authoritative
> regarding the de
I've been thinking about the role that stories played compared to
specs, and that "should we use should" thread brought those thoughts
up again.
First I want to discuss whether or not specs are authoritative
regarding the desired behavior of a system. I would say they're a
good approximation of h
20 matches
Mail list logo
