2009/4/1, [email protected] <[email protected]>: > Send rspec-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://rubyforge.org/mailman/listinfo/rspec-users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of rspec-users digest..." > > > Today's Topics: > > 1. Re: RSpec makes me want to write better code (aidy lewis) > 2. Re: RSpec makes me want to write better code (David Chelimsky) > 3. Re: Good introduction to rspec (Stephen Eley) > 4. Re: Good introduction to rspec (Stephen Eley) > 5. Re: Good introduction to rspec (Scott LaBounty) > 6. Re: Good introduction to rspec (David Chelimsky) > 7. Re: Good introduction to rspec (Scott LaBounty) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 1 Apr 2009 14:01:19 +0100 > From: aidy lewis <[email protected]> > Subject: Re: [rspec-users] RSpec makes me want to write better code > To: rspec-users <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi David > > 2009/3/31 David Chelimsky <[email protected]>: > >> The point of TDD is writing small examples and small bits of code in a >> cycle. The point of BDD is to write high level scenarios so you know >> what code to write, but then drive it out in detail with TDD. > > Does this necessitate that the same person or pair should be doing > both the TDD and BDD for the same area? My problem at the moment is > that as a software tester I would in combination with a customer > create the feature Acceptance Criteria (AC). The AC would be used by > the developer to guide his\her design, but he\she would be unlikely to > implement the automated test, which would normally be done by the > tester (using Watir\Cucumber). My feeling is that if we are to get the > optimal benefit from TDD\BDD then the developer(s) should be > automating the AC. What do you think? > > I don't think this removes the need of the tester as he/she may be > more likely to have a skill-set that is aware of > bigger-than-unit-test-tools and frameworks, but I think they should be > pairing with the developer. However the problem then arises if the > developer and tester use different languages. I use Ruby while the > production code is in .Net. The TDD interplay would be more seamless I > think with a single language. But as a tester it would be insane for > me to use a static and compiled language to - in effect - test a web > site. > > Aidy > > > ------------------------------ > > Message: 2 > Date: Wed, 1 Apr 2009 08:35:01 -0500 > From: David Chelimsky <[email protected]> > Subject: Re: [rspec-users] RSpec makes me want to write better code > To: rspec-users <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > On Wed, Apr 1, 2009 at 8:01 AM, aidy lewis <[email protected]> > wrote: >> Hi David >> >> 2009/3/31 David Chelimsky <[email protected]>: >> >>> The point of TDD is writing small examples and small bits of code in a >>> cycle. The point of BDD is to write high level scenarios so you know >>> what code to write, but then drive it out in detail with TDD. >> >> Does this necessitate that the same person or pair should be doing >> both the TDD and BDD for the same area? My problem at the moment is >> that as a software tester I would in combination with a customer >> create the feature Acceptance Criteria (AC). The AC would be used by >> the developer to guide his\her design, but he\she would be unlikely to >> implement the automated test, which would normally be done by the >> tester (using Watir\Cucumber). My feeling is that if we are to get the >> optimal benefit from TDD\BDD then the developer(s) should be >> automating the AC. What do you think? > > Given that I don't know the skill-set available on your team, it's > difficult for me to say what would provide optimum benefit for *your > team*. That said, in some idealistic BDD fashion, I'd think the best > deal would be the tester and developer pairing on automating AC. Then > that developer would pair with another developer driving out the code > w/ TDD. > >> I don't think this removes the need of the tester as he/she may be >> more likely to have a skill-set that is aware of >> bigger-than-unit-test-tools and frameworks, but I think they should be >> pairing with the developer. > > I honestly wrote the above before I read this :) Yes, I agree, tester > and developer pairing is *generally* a good thing. > >> However the problem then arises if the >> developer and tester use different languages. I use Ruby while the >> production code is in .Net. The TDD interplay would be more seamless I >> think with a single language. But as a tester it would be insane for >> me to use a static and compiled language to - in effect - test a web >> site. > > I'm going to go out on a limb here and suggest that if you're > proficient in Ruby and you're pairing with a reasonably skilled > developer in any C-based language like C Sharp, the language barrier > will be fairly small. There are some hoops, like meta-programming, > blocks and iterators, but not too many beyond that. I don't mean that > to be flippant. Even if the dev has zero experience with these > concepts, he really doesn't need to understand them in order to > progress if you're pairing. > > HTH, > David > >> >> Aidy >> _______________________________________________ >> rspec-users mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/rspec-users >> > > > ------------------------------ > > Message: 3 > Date: Wed, 1 Apr 2009 06:57:42 -0700 > From: Stephen Eley <[email protected]> > Subject: Re: [rspec-users] Good introduction to rspec > To: rspec-users <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > 2009/4/1 Pablo L. de Miranda <[email protected]>: >> @Fernando - So what material you recommend to start a study in rSpec? > > 1.) The Web site documentation at http://rspec.info > > 2.) Use it and build experience. > > 3.) Get the beta of the RSpec book. > > 4.) Use it and build experience. > > 5.) Google is your friend. > > 6.) Use it and build experience. > > Finally, if in doubt... Try using it and building some experience. > > > -- > Have Fun, > Steve Eley ([email protected]) > ESCAPE POD - The Science Fiction Podcast Magazine > http://www.escapepod.org > > > ------------------------------ > > Message: 4 > Date: Wed, 1 Apr 2009 07:23:32 -0700 > From: Stephen Eley <[email protected]> > Subject: Re: [rspec-users] Good introduction to rspec > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > On Tue, Mar 31, 2009 at 11:50 PM, Fernando Perez <[email protected]> > wrote: >> >> I don't spec at all the way he shows, I might be doing things wrong, but >> I am very happy with my workflow. > > http://www.kipling.org.uk/poems_neolithic.htm > > (The poem's by Rudyard Kipling, if the URL doesn't make it clear.) > > > -- > Have Fun, > Steve Eley ([email protected]) > ESCAPE POD - The Science Fiction Podcast Magazine > http://www.escapepod.org > > > ------------------------------ > > Message: 5 > Date: Wed, 1 Apr 2009 07:53:03 -0700 > From: Scott LaBounty <[email protected]> > Subject: Re: [rspec-users] Good introduction to rspec > To: rspec-users <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > I've looked at the web site and I guess I'm looking for more examples. I'd > like to see some simple basic ruby code and then some rSpec code testing it. > No Rails, no nothing else. I haven't tried the book yet, but there does not > seem to be a lot of code out there at this basic a level. > > Any ideas? > > Scott > > On Wed, Apr 1, 2009 at 6:57 AM, Stephen Eley <[email protected]> wrote: > >> 2009/4/1 Pablo L. de Miranda <[email protected]>: >> > @Fernando - So what material you recommend to start a study in rSpec? >> >> 1.) The Web site documentation at http://rspec.info >> >> 2.) Use it and build experience. >> >> 3.) Get the beta of the RSpec book. >> >> 4.) Use it and build experience. >> >> 5.) Google is your friend. >> >> 6.) Use it and build experience. >> >> Finally, if in doubt... Try using it and building some experience. >> >> >> -- >> Have Fun, >> Steve Eley ([email protected]) >> ESCAPE POD - The Science Fiction Podcast Magazine >> http://www.escapepod.org >> _______________________________________________ >> rspec-users mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/rspec-users >> > > > > -- > Scott > http://steamcode.blogspot.com/ > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://rubyforge.org/pipermail/rspec-users/attachments/20090401/8bced54b/attachment-0001.html> > > ------------------------------ > > Message: 6 > Date: Wed, 1 Apr 2009 10:44:02 -0500 > From: David Chelimsky <[email protected]> > Subject: Re: [rspec-users] Good introduction to rspec > To: rspec-users <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > 2009/4/1 Scott LaBounty <[email protected]>: >> I've looked at the web site and I guess I'm looking for more examples. I'd >> like to see some simple basic ruby code and then some rSpec code testing >> it. >> No Rails, no nothing else. I haven't tried the book yet, but there does >> not >> seem to be a lot of code out there at this basic a level. >> >> Any ideas? > > Try this: > > http://blog.davidchelimsky.net/2007/5/14/an-introduction-to-rspec-part-i > > Cheers, > David > > > >> >> Scott >> >> On Wed, Apr 1, 2009 at 6:57 AM, Stephen Eley <[email protected]> wrote: >>> >>> 2009/4/1 Pablo L. de Miranda <[email protected]>: >>> > @Fernando - So what material you recommend to start a study in rSpec? >>> >>> 1.) The Web site documentation at http://rspec.info >>> >>> 2.) Use it and build experience. >>> >>> 3.) Get the beta of the RSpec book. >>> >>> 4.) Use it and build experience. >>> >>> 5.) Google is your friend. >>> >>> 6.) Use it and build experience. >>> >>> Finally, if in doubt... ?Try using it and building some experience. >>> >>> >>> -- >>> Have Fun, >>> ? Steve Eley ([email protected]) >>> ? ESCAPE POD - The Science Fiction Podcast Magazine >>> ? http://www.escapepod.org >>> _______________________________________________ >>> rspec-users mailing list >>> [email protected] >>> http://rubyforge.org/mailman/listinfo/rspec-users >> >> >> >> -- >> Scott >> http://steamcode.blogspot.com/ >> >> _______________________________________________ >> rspec-users mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/rspec-users >> > > > ------------------------------ > > Message: 7 > Date: Wed, 1 Apr 2009 08:47:33 -0700 > From: Scott LaBounty <[email protected]> > Subject: Re: [rspec-users] Good introduction to rspec > To: rspec-users <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > David, > > That's more what I was looking for. > > Thanks, > > Scott > > On Wed, Apr 1, 2009 at 8:44 AM, David Chelimsky <[email protected]>wrote: > >> 2009/4/1 Scott LaBounty <[email protected]>: >> > I've looked at the web site and I guess I'm looking for more examples. >> I'd >> > like to see some simple basic ruby code and then some rSpec code testing >> it. >> > No Rails, no nothing else. I haven't tried the book yet, but there does >> not >> > seem to be a lot of code out there at this basic a level. >> > >> > Any ideas? >> >> Try this: >> >> http://blog.davidchelimsky.net/2007/5/14/an-introduction-to-rspec-part-i >> >> Cheers, >> David >> >> >> >> > >> > Scott >> > >> > On Wed, Apr 1, 2009 at 6:57 AM, Stephen Eley <[email protected]> wrote: >> >> >> >> 2009/4/1 Pablo L. de Miranda <[email protected]>: >> >> > @Fernando - So what material you recommend to start a study in rSpec? >> >> >> >> 1.) The Web site documentation at http://rspec.info >> >> >> >> 2.) Use it and build experience. >> >> >> >> 3.) Get the beta of the RSpec book. >> >> >> >> 4.) Use it and build experience. >> >> >> >> 5.) Google is your friend. >> >> >> >> 6.) Use it and build experience. >> >> >> >> Finally, if in doubt... Try using it and building some experience. >> >> >> >> >> >> -- >> >> Have Fun, >> >> Steve Eley ([email protected]) >> >> ESCAPE POD - The Science Fiction Podcast Magazine >> >> http://www.escapepod.org >> >> _______________________________________________ >> >> rspec-users mailing list >> >> [email protected] >> >> http://rubyforge.org/mailman/listinfo/rspec-users >> > >> > >> > >> > -- >> > Scott >> > http://steamcode.blogspot.com/ >> > >> > _______________________________________________ >> > rspec-users mailing list >> > [email protected] >> > http://rubyforge.org/mailman/listinfo/rspec-users >> > >> _______________________________________________ >> rspec-users mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/rspec-users >> > > > > -- > Scott > http://steamcode.blogspot.com/ > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://rubyforge.org/pipermail/rspec-users/attachments/20090401/587cb956/attachment.html> > > ------------------------------ > > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users > > End of rspec-users Digest, Vol 34, Issue 2 > ****************************************** >
-- Enviado do meu celular Atenciosamente, Charleno Pires Desenvolvedor Web - Teresina Piauí www.charlenopires.com.br (building) Msn: [email protected] GTalk: [email protected] _______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
