tag:blogger.com,1999:blog-24599054.post116827159816135947..comments2024-02-07T00:23:34.835-07:00Comments on On Ruby: RSpec and Unit Tests: Localizing Problems or Reducing Couplinggnupatehttp://www.blogger.com/profile/10492341480170667775noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-24599054.post-1168652420811288022007-01-12T18:40:00.000-07:002007-01-12T18:40:00.000-07:00Can I make a non-philosophical plug for RSpec? I j...Can I make a non-philosophical plug for RSpec? I just like the way it stays out of your way. The Contect/Specify thing is a mini-DSL. In xUnit and Test::Unit I was always trying to invent class names and method names to indicate what I wanted to test. I was always unclear where the scope started and ended. NUnit hd a nice little [TestFixture] thing you could use to scope things with. <BR/><BR/>Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-24599054.post-1168351706923490612007-01-09T07:08:00.000-07:002007-01-09T07:08:00.000-07:00James,that fits pretty well with the conversation ...James,<BR/>that fits pretty well with the conversation Kevin Tew and I had shortly after I posted this. (I'll be posting a follow-up based on that conversation in the next day or two.)gnupatehttps://www.blogger.com/profile/10492341480170667775noreply@blogger.comtag:blogger.com,1999:blog-24599054.post-1168295428934980472007-01-08T15:30:00.000-07:002007-01-08T15:30:00.000-07:00I'll take a stab at your first question (re: unit ...I'll take a stab at your first question (re: unit tests). Bear in mind that I'm speaking in terms of my understanding and vision of both RSpec and Unit Tests.<BR/><BR/>RSpec is sort of like writing a contract: you define what to expect, and what not to expect, from a given model under general cases. Unit tests, on the other hand, probe specific cases or instances where behavior can go awry. InJames H.https://www.blogger.com/profile/07452586529428476134noreply@blogger.com