tag:blogger.com,1999:blog-25066620.post8618387797468799403..comments2007-08-11T09:37:50.291-05:00Comments on Ruby, Rails, Merb blog: Snakes, Gems & Coffee: Story-level BDD specing using rBehaveS. Potterhttp://www.blogger.com/profile/17341145424164713662noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-25066620.post-174667727208741512007-08-11T09:37:00.000-05:002007-08-11T09:37:00.000-05:00You do bring up an interesting point and it is a p...You do bring up an interesting point and it is a problem also common in RSpec when you wish to create a "shared" set of behavior specifications (new to 1.x I believe). For the most part though I haven't had too many issues with that and I've been using that feature with RSpec heavily for almost 2 months now. Howeer, longer-term we will see.S. Potterhttp://www.blogger.com/profile/17341145424164713662noreply@blogger.comtag:blogger.com,1999:blog-25066620.post-25717739781584409092007-08-11T01:14:00.000-05:002007-08-11T01:14:00.000-05:00Looks beautiful.But, won't this long strings, whic...Looks beautiful.<BR/>But, won't this long strings, which you use as identity, won't they pretty much error prone? It's quite easy to missprint something is such cases.<BR/>But sure, its interesting and feels more natural than the original rSpec.Anonymousnoreply@blogger.com