Re: Recommendations re tests wrt a reference implementation

I'd be minded to go with a hybrid approach -- write my tests for the both the old and new code, then use the results of the Reference Implementation as the standard to validate my new code against. Obviously, the new features may not (probably will not) have analogs in the RI, but where there is comparable functionality, use it. (And remember the first rule of System Analysis: "The System you are designing must function at least as well as the System it is going to replace.")

----
I Go Back to Sleep, Now.

OGB

Comment on Re: Recommendations re tests wrt a reference implementation

Replies are listed 'Best First'.
Re^2: Recommendations re tests wrt a reference implementation by blazar (Canon) on Jun 19, 2007 at 17:09 UTC
Obviously, the new features may not (probably will not) have analogs in the RI, but where there is comparable functionality, use it. This is exactly what I meant. (And remember the first rule of System Analysis: "The System you are designing must function at least as well as the System it is going to replace.") And this is exactly what I had in mind... in fact the whole question arises out of the need for the new application to work exactly as the old faithful one when no new feature is used.	[reply]

Replies are listed 'Best First'.

Re^2: Recommendations re tests wrt a reference implementation
by blazar (Canon) on Jun 19, 2007 at 17:09 UTC

Obviously, the new features may not (probably will not) have analogs in the RI, but where there is comparable functionality, use it.

This is exactly what I meant.

(And remember the first rule of System Analysis: "The System you are designing must function at least as well as the System it is going to replace.")

And this is exactly what I had in mind... in fact the whole question arises out of the need for the new application to work exactly as the old faithful one when no new feature is used.

[reply]