From: Gennady Bystritsky Date: 2007-01-20T15:19:19+09:00 Subject: Re: I don't get rspec ------_=_NextPart_001_01C73C5A.E864A588 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable It is worth noting that rSpec is not the only player in the field of = behavior testing. It simply goes a bit further providing the whole = framework in place of Test/Unit (it reads much better, for one). I use = Mocha with Test/Unit for behavior/unit testing an is quite happy with = the combo. I saw it mentioned somewhere that Mocha comes by default in = RoR installations, so they have means for behavior testing already ;-). Gennady. -----Original Message----- From: Sam Smoot [mailto:ssmoot@gmail.com] Sent: Fri 1/19/2007 16:55 To: ruby-talk ML Subject: Re: I don't get rspec =20 nicknameoptional wrote: > besides more English like, how is it better than the assert_equal? It's not. If you're doing TDD right, then BDD is just what you're doing already, by another name. The problem is a lot of people don't do TDD right, and the semantics of it raise the barrier to entry. BDD is about trying to change those semantics, so TDD As-It-Was-Meant-To-Be becomes more popular. It's just a bonus that rSpec reads so nicely and prints out nice looking reports. So I was in the same boat as you. Then I decided: "You know, they have a point about people misinterpreting TDD. So is trying to change the language used to describe it really such an awful thing?" And that's where I am now. Is using rSpec in your projects going to increase velocity by 10%? Or make it easier to communicate with business people? Or allow you to write better tests? Have fewer bugs? Any of these things? No. Not if you're already doing TDD well. It might help more developers to get there though. It might help new team-members integrate faster with less training on TDD and the way you're doing things. It might just give you a warm fuzzy. Compared to a lot of the arbitrary and complex choices we sometimes make, you could do a lot worse I think. ------_=_NextPart_001_01C73C5A.E864A588--