On Wed, Sep 17, 2008 at 5:58 PM, aslak hellesoy
> Can we all please stop talking about "best" practices? It always
> depends. If people talk about best practices then others will be more
> inclined to apply them without thinking.
>
> http://www.satisfice.com/blog/archives/27
> http://www.infoq.com
On Tue, Sep 16, 2008 at 7:00 PM, Martin Streicher
<[EMAIL PROTECTED]> wrote:
>
> A few questions from someone new to rspec.
>
> 1/ I have several complex yet largely independent models using rspec to test
> internals and computation methods. I am about to tackle models that have
> several ties to e
On Wed, Sep 17, 2008 at 4:54 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> On 16 Sep 2008, at 23:38, James Cox wrote:
>
>> BTW - do any 'proper' tdd/bdd types here reccommend any specific books?
>
> The Michael Feathers book (Working with Legacy Code) is well regarded on
> this list for teaching you
On Wed, Sep 17, 2008 at 2:54 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> On 16 Sep 2008, at 23:38, James Cox wrote:
>
> BTW - do any 'proper' tdd/bdd types here reccommend any specific books?
>>
>
>
I've just started reading "Scripted GUI Testing with Ruby," which has
sections on RSpec, ZenTest a
On 16 Sep 2008, at 23:38, James Cox wrote:
BTW - do any 'proper' tdd/bdd types here reccommend any specific
books?
The Michael Feathers book (Working with Legacy Code) is well regarded
on this list for teaching you how to write testable code, if that
helps. I don't think there are any boo
Oh and to answer your question Martin -
it's a fairly common step for both. Your absolute best bet is going to
peepcode.com and watching all the vids on speccing. it should give you
more than enough starting information about approach.
BTW - do any 'proper' tdd/bdd types here reccommend any
On 16 Sep 2008, at 20:05, David Chelimsky wrote:
On Tue, Sep 16, 2008 at 1:59 PM, Mark Wilden <[EMAIL PROTECTED]> wrote:
On Tue, Sep 16, 2008 at 10:00 AM, Martin Streicher
<[EMAIL PROTECTED]> wrote:
3/ Has any documented how to run the debugger via rspec to help
track down
errors?
We TD
>
> law of demeter
I prefer to call it the "Suggestion of a Bunch of Guys on a Project called
'Demeter' That Is Useful to Keep in Mind in Many Situations". But that's not
as catchy.
It sure as hell ain't no law.
///ark
___
rspec-users mailing list
rsp
On Sep 17, 2008, at 9:01 AM, Martin Streicher wrote:
I find the debugger helpful to step through the underlying Rails
code when I am perplexed about the (errant) operation of something.
The underworld is full of wonderful secrets. Plus, I do make
mistakes and misinterpret and the debugge
I find the debugger helpful to step through the underlying Rails code
when I am perplexed about the (errant) operation of something. The
underworld is full of wonderful secrets. Plus, I do make mistakes and
misinterpret and the debugger lets me take a look around. I try to
avoid making ba
On Tue, Sep 16, 2008 at 6:11 PM, Scott Taylor <[EMAIL PROTECTED]
> wrote:
> Yeah - I use a debugger all the time
I regard using the debugger as a bit of a smell. It often means my code
isn't clear enough to just bench-step through. In a way, it's like
commenting. Complicated code often needs co
On Sep 16, 2008, at 3:05 PM, David Chelimsky wrote:
On Tue, Sep 16, 2008 at 1:59 PM, Mark Wilden <[EMAIL PROTECTED]> wrote:
On Tue, Sep 16, 2008 at 10:00 AM, Martin Streicher
<[EMAIL PROTECTED]> wrote:
3/ Has any documented how to run the debugger via rspec to help
track down
errors?
We
On Tue, Sep 16, 2008 at 1:59 PM, Mark Wilden <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 16, 2008 at 10:00 AM, Martin Streicher
> <[EMAIL PROTECTED]> wrote:
>>
>> 3/ Has any documented how to run the debugger via rspec to help track down
>> errors?
>
> We TDD/BDD/Agile practitioners aren't supposed to
On Tue, Sep 16, 2008 at 10:00 AM, Martin Streicher <
[EMAIL PROTECTED]> wrote:
>
> 3/ Has any documented how to run the debugger via rspec to help track down
> errors?
>
We TDD/BDD/Agile practitioners aren't supposed to use a debugger, so don't
tell anyone I said this. But all I have to do (on a
14 matches
Mail list logo
