Browse by Tags -

Browse by Tags

Three simple Rhino Mocks rules

In previous versions of Rhino Mocks, the Record/Replay model was the only way to create and verify mocks. You would have an area that set up expectations in a record mode, then the replay mode would verify your expectations. What was really strange about the Record/Replay model was that it...

Posted to Jimmy Bogard (Weblog) by bogardj on 10-05-2008
A TDD investment addendum

I completely left out one very important tip in my top 10 tips to get a return on your TDD investment : Take advantage of pair-programming . Pair programming is a great teaching device, as it lets two people go back and forth, working on a problem. By pairing someone new to TDD with someone experienced...

Posted to Jimmy Bogard (Weblog) by bogardj on 09-22-2008
Ten tips to maximize the return on your TDD investment

Paul Cowen presented an interesting personal observation of using TDD on the ALT.NET mailing list, under the title " TDD + effort != return ". The implication being that doing TDD requires extra work during development, extra work in training, extra work in hiring qualified people, even extra...

Posted to Jimmy Bogard (Weblog) by bogardj on 09-21-2008
Interfaces and isolation

Roy Osherove has suggested a new name for mocks, fakes, stubs or any test double: Isolation . True, the myriad of test double names can muddy the language, and Meszaros' suggested name of "test double" still confuses people that don't get the "stunt double" comparison. When...

Posted to Jimmy Bogard (Weblog) by bogardj on 09-20-2008
TDD design trade-offs and junk food

Tony Rasa recently talked about design trade-offs when doing TDD: When “doing TDD,” we consciously make design trade-offs to favor testability. ... we end up with a lot of single-implementation interfaces because of testability concerns and from weaknesses with our tools. When I first started doing TDD...

Posted to Jimmy Bogard (Weblog) by bogardj on 09-18-2008
Announcing: Pablo’s Days of TDD in Austin, TX

Los Techies(.com) , its president, Pablo El Burro, and our sponsors are pleased to announce "Pablo's Days of TDD" (PDoTDD). PDoTDD is a day-and-a-half event of workshops, discussion, practice, and training around automated unit testing, specifically the practice of Test-Driven Development...

Posted to Chad Myers' Blog (Weblog) by chadmyers on 09-15-2008
Quality and code coverage

It's an age-old question: should our team's goal be 100% coverage? A valid question, but one I've never much cared about in practice. The idea is that the team, all practicing TDD, should dutifully measure and add unit tests until they reach the assumed pinnacle of unit testing: 100% coverage...

Posted to Jimmy Bogard (Weblog) by bogardj on 09-09-2008
Design and Testability

There was a rather healthy public discussion and debate going on via Twitter today between Roy Osherove, Ayende Rahien, Colin Jack, me, and several others. Michael Feathers even dropped in at one point which was cool. This all started when Roy twittered an interesting link to a post by Jacob Proffitt...

Posted to Chad Myers' Blog (Weblog) by chadmyers on 08-16-2008
Droppin' Pennies on context specs...

First off I want to make it clear that I'm not a guru on the topic, but I do find it interesting. The topic of course is Context Based Specifications. I've seen an emergence in interest in writing context based specifications lately on the blogosphere. However, everyone seems to be advertising...

Posted to Mo Khan's Blog (Weblog) by mo.khan on 08-15-2008
Parsing The Payload

So this week we got to start working a brand spanking new MVC project. So far we're leveraging Castle Windsor, NHibernate, Fluent Nhibernate, and kind of running Linq to NHibernate. It's amazing how quickly you can get a project up and running in such a short amount of time. (BTW, Fluent NHibernate...

Posted to Mo Khan's Blog (Weblog) by mo.khan on 08-14-2008

Page 1 of 5 (48 items) 1 2 3 4 5 Next >