Jeremy D. Miller -- The Shade Tree Developer

Browse by Tags

• Build your own CAB
• Continuous Integration
• Database and Persistence
• Design Patterns
• Featured
• Legacy Code
• Maintainability
• Pair Programming
• Ranting
• Starting a new Project
• StoryTeller
• StructureMap

• Test what you're testing

  I use the phrase in the title usually to refer to using mock objects in a useless way (mocking ADO.Net or Active Directory or calls to any API that you don't understand). When you're choosing whether to write a small integration test or a mocked... Posted Mar 10 2008, 06:02 PM by Jeremy D. Miller with | with 11 comment(s) Filed under: Test Driven Development

• Unit testing, playing tennis, and the lack of absolutes in TDD

  I'm not a particularly good tennis player. Mostly from not having played in years, but even then, I suffered because I can't hit a decent backhand to save my life. I have a big serve and a decent control with my forehand, but all you've got... Posted Mar 03 2008, 08:03 AM by Jeremy D. Miller with | with 23 comment(s) Filed under: Test Driven Development

• TypeMock isn't too powerful, and "Designing for Testability" is much more than merely mocking anyway

  Roy has a post up today about TypeMock, testability, and DI . The age old (ok, it just seems like we've been arguing over this for decades) question comes up again "is TypeMock too powerful?" First, let's go pro-TypeMock because the... Posted Jan 18 2008, 07:05 PM by Jeremy D. Miller with | with 17 comment(s) Filed under: Test Driven Development

• Spiking a new syntax for integration tests. Whaddaya think?

  Hello, my name is Jeremy, and I sometimes write unit tests specifications that are uglier than sin. Specifically, when I started to look back at the interaction style tests I've been writing over the past couple years I'm finding a bunch of unit... Posted Jan 17 2008, 02:27 AM by Jeremy D. Miller with | with 18 comment(s) Filed under: StructureMap, Test Driven Development

• TDD/BDD and Design by Contract: I don't really see any conflict between the two

  I found an interesting link today from Mario Gleichmann called Test Driven Development and Design By Contract - friend or foe?. I've always been lukewarm toward Design by Contract (DbC). Occasionally I'll run into claims from DbC enthusiasts that... Posted Dec 11 2007, 08:26 AM by Jeremy D. Miller with | with 7 comment(s) Filed under: Test Driven Development

• From a TDD Fanboy's viewpoint, how you know your approach to TDD or just plain unit testing is working?

  I've had a couple conversations the past couple weeks about extending test coverage in the user interface and the necessity of writing integrated tests. One person wished his team were doing more automated testing through the UI (web app), and the... Posted Oct 01 2007, 06:42 PM by Jeremy D. Miller with | with 20 comment(s) Filed under: Featured, Test Driven Development

• BDD, TDD, and the other Double D's

  Behavior Driven Development (BDD) has been a pretty big topic in some of the email groups I lurk in. I'm seeing BDD cast as a whole new paradigm of development, where as I see BDD as an evolution of TDD with a better syntax and mechanics for expressing... Posted Sep 06 2007, 09:20 AM by Jeremy D. Miller with | with 16 comment(s) Filed under: Test Driven Development

• Designing for Testability

  EDIT: What I should really say is that it isnt' just Designing for Testability, it's Designing with Testability From a question on my Passive View blog post : "should we design for testability, or should we try and test what's designed... Posted Jun 29 2007, 08:30 AM by Jeremy D. Miller with | with 12 comment(s) Filed under: Test Driven Development

• Build your own CAB Part #10 - Unit Testing the UI with NUnitForms

  I've long, long since left the rails of "Build your own CAB" topics and wandered off into "just things you do" when you're building a WinForms application. I'm doing this topic now because it felt easy to do in the midst... Posted Jun 26 2007, 09:57 PM by Jeremy D. Miller with | with 11 comment(s) Filed under: Build your own CAB, Featured, Test Driven Development

• Build your own CAB Part #2 - The Humble Dialog Box

  When last we left our hero , D'Artagnan was chasing the evil Lady de Winter across the breadth of France trying to intercept her on her dastardly mission when he found himself beset by disparate responsibilities within the tight confines of a single... Posted May 23 2007, 07:29 AM by Jeremy D. Miller with | with 30 comment(s) Filed under: Build your own CAB, Design Patterns, Test Driven Development

• Jeremy's Fourth Law of Test Driven Development: Keep Your Tail Short

  One of the first ongoing lesson for making Test Driven Development succeed for you is to learn how to write isolated tests with less effort. My Fourth Law of TDD is all about recognizing the need to do testing piecewise as a vital part of formulating software designs. One way or another, all design concepts come down to dividing the whole into granular pieces. Keeping a short tail is yet one more design cue to help guide you where you want the design to go. Posted Apr 27 2007, 08:42 AM by Jeremy D. Miller with | with 11 comment(s) Filed under: Maintainability, Test Driven Development

• More testing code than production code is typical, but don't let that stop you

  Ian Cooper recently wrote about the Ratio of test code to production code . Ian is saying that he's routinely seeing a 1:1 or even 1.5:1 ratio of test code to production code. From my experience with TDD, that's about normal. Some kinds of code... Posted Mar 22 2007, 03:45 PM by Jeremy D. Miller with | with 11 comment(s) Filed under: Test Driven Development

• Jay's TDD QuickStart, and the underlying problems he stumbled into

  Jay Kimble , CodeBetter's resident AJAX guru, issued a little challenge to us TDD bloggers about using Test Driven Development to develop a custom extension to the MS Ajax ScriptManager control . In the comments, Jeff Perrin (you need to blog more... Posted Mar 07 2007, 02:05 PM by Jeremy D. Miller with | with 38 comment(s) Filed under: Maintainability, Test Driven Development

• What about Usability?

  Sort of a continuation of the ongoing maintainability series, it's time to look at some of the benefits. And rant because that's just what I do. After publishing My Programming Manifesto (about the things *I* was thinking about at the time) post... Posted Jan 14 2007, 10:16 PM by Jeremy D. Miller with | with 5 comment(s) Filed under: Maintainability, Continuous Integration, Test Driven Development, Ranting

• Week 2: Scheduling and Coordinating the Work

  Continuing the " Getting Started " series. My team just finished our second week. Luckily enough we were able to get through release planning quickly and start Iteration #1 on Tuesday. CruiseControl.Net is up and running. I kept a list of the... Posted Oct 15 2006, 11:05 AM by Jeremy D. Miller with | with 2 comment(s) Filed under: Continuous Integration, Test Driven Development, Starting a new Project, Pair Programming