Re: Re(2): So I'm in a bit of a quandary

I'm big on unit testing. The unit test becomes the regression test after a change is made. If someone reports a problem and it gets down to a small code sample, I add that to the unit test before fixing it.

Somehow I doubt that his existing code has unit test code with it. So just what is it supposed to do? Mudding the difference between what it's defined to do vs what it just happens to do is one of my pet issues, too.

Comment on Re: Re(2): So I'm in a bit of a quandary

Replies are listed 'Best First'.
Re(4): So I'm in a bit of a quandary by FoxtrotUniform (Prior) on Jul 08, 2002 at 19:28 UTC
Somehow I doubt that his existing code has unit test code with it. So just what is it supposed to do? Mudding the difference between what it's defined to do vs what it just happens to do is one of my pet issues, too. In this case, I'd probably try to test against what the old code actually does, especially if it's been in production for a while (with people depending on its quirks). Exercise each feature of the old code (and any combinations that seem to be interdependent), capture the output, and diff. (Not nearly as easily done as said, I know. :-( ) `-- The hell with paco, vote for Erudil! :wq`	[reply]

Replies are listed 'Best First'.

Re(4): So I'm in a bit of a quandary
by FoxtrotUniform (Prior) on Jul 08, 2002 at 19:28 UTC

In this case, I'd probably try to test against what the old code actually does, especially if it's been in production for a while (with people depending on its quirks). Exercise each feature of the old code (and any combinations that seem to be interdependent), capture the output, and diff. (Not nearly as easily done as said, I know. :-( )

-- The hell with paco, vote for Erudil! :wq

[reply]