Jimmy Bogard » All Tags » TDD (RSS)

Browse by Tags

  • Reflecting reality

    Reading over the latest MSDN magazine issue, I’m always encouraged when I see something that I consider important on the cover, Test-Driven Design .  It covers one of the more difficult technical aspects of TDD, which is mock objects.  It took...
    Filed under:

  • Subverting TDD as a design tool

    So TypeMock can now mock DateTime.Now .  Replacing the functionality of DateTime.Now, which is an external dependency, was one of the first issues that taught me the value of TDD.  With TypeMock replacing DateTime.Now, I get all the benefits...
    Filed under:

  • Disambiguating a test fixture

    One of the more disappointing things I found reading the xUnit Test Patterns book was how much one tool could shape my views on a concept.  NUnit, as great and simple tool as it is, doesn’t quite match the other xUnit tools out there when it comes...
    Filed under:

  • Getting value out of your unit tests

    Unit tests, with TDD in particular, are the most efficient way I’ve found in creating behavior for my application.  For lasting value, beyond just the safety net of “if I change something, will something break”, requires extra discipline, and a more...
    Filed under:

  • Where TDD fails for me

    TDD is by far the sharpest tool in my belt.  The simplicity of client-driven design combined with the safety net of unit tests allow me to build software at a remarkable constant pace.  At the edges of most of the applications I’ve worked on...
    Filed under:

  • Acceptable test failures

    As Derick Bailey pointed out in my last post, one of the annoyances with ReSharper is the NotImplementedException it puts in when you generate a method.  Going from the TDD side, this is exactly what we don’t want when we’re doing Red-Green-Refactor...
    Filed under:

  • 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...
    Filed under: ,

  • 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...
    Filed under:

  • 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...
    Filed under:

  • 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...
    Filed under:

  • 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...
    Filed under:

  • 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...
    Filed under: ,

  • PabloTV: Eliminating static dependencies screencast

    Nature abhors a vacuum. It turns out she also abhors static dependencies (I have my sources). Static dependencies are the modern-day globals, often exposed through classes named "Helper". I've certainly been guilty of overusing static dependencies...

  • Should you TDD when flying solo?

    A couple of weeks ago a question came up on the ALT.NET message board : Does TDD make sense when you're the only developer in your company? To me, this is akin to the following questions: Is quality important? Is maintainability important? Is design...
    Filed under:

  • Auto-mocking container pitfalls?

    I'm taking a closer look at the auto-mocking container idea, specifically as we're including it in the upcoming release of NBehave. I'm a little wary of prolonged use, but wanted to get some feedback (it's also on the ALT.NET message board...
    Filed under: ,
1 2 Next >
Copyright Los Techies 2008, 2009. All rights reserved.
Powered by Community Server (Commercial Edition), by Telligent Systems