in reply to Re: The Evil Pleasures of Unit Tests
in thread The Evil Pleasures of Unit Tests
You did say teammates right?Right. And I don't expect to have to do this for more than another week.
If you're on a project where people are checking in stuff that doesn't work, or only, uh, partially works, there are a couple of ways to handle it. You could quietly fix stuff yourself, but then they won't learn (and they'd probably get pissed at you for reaching into their code). Or you can mark up a listing and hand it to them. Or you can say, without pointing out any specific fault, "I don't care how you implement this, but we've agreed on the interface, and I'm going to hold you to that agreement." A unit test does the latter, and shifts the pain, if any, where it belongs. And if others on the team need to do this to me, then I deserve it.
Standing up for your agreements early in a project can save you a lot of work later on.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Re: Re: The Evil Pleasures of Unit Tests
by tachyon (Chancellor) on Aug 30, 2003 at 12:27 UTC | |
Re: Re: Re: The Evil Pleasures of Unit Tests
by pdcawley (Hermit) on Aug 31, 2003 at 06:21 UTC | |
by dws (Chancellor) on Aug 31, 2003 at 08:54 UTC | |
by halley (Prior) on Sep 02, 2003 at 17:59 UTC | |
by dws (Chancellor) on Sep 02, 2003 at 18:53 UTC | |
by pdcawley (Hermit) on Sep 03, 2003 at 14:30 UTC | |
by dws (Chancellor) on Sep 03, 2003 at 16:12 UTC |