SteveC said: > My development cycle typically includes tiered coders, each are given an > explicit document of "what to do", even in calling stored procedures. > The problem is that all of the stored procedures are not ready or > written (or sometimes fully thought out and need to be changed) on the > DB side of things. So it would be to the .NET component developer's > advantage to have the DB-calling code in place, but instead of calling > the real thing, it just calls this pseudo-MSSQL-host. Then the .NET > coders could perform unit testing and etc without having things break > when they are actually supposed to get data from "somewhere".
It sounds like you want to use a mock object pattern. A java example is http://javaboutique.internet.com/tutorials/mock_objects/, but the technique obviously applies elsewhere. Eric. =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
