----- Original Message ----- From: "Glen Daniels" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, October 14, 2002 6:14 PM Subject: RE: dotnet local tests
> > While it's certainly a great thing to be able to set up local .NET tests, I added a "playback" handler today which can fill the role of the server for simple "one-roundtrip" tests, simulating whatever response we desire. I'd like to filter the tests into "simple" and "complex" ones, where the "simple" ones are those which can just use the playback feature to check how we deal with receiving particular messages - we can integrate these into our functional tests very easily. The "complex" ones require actual code running on .NET. > > --Glen a playback server would be good, but since stage 2 of .net testing is to to do .net client, you still need install the framework. Complex tests are anything that test round tripping, or particular .net versions (like 1.1 as well as 1.0) :- -are object references being preserved? -what does that version of .net do for out-of-range enums? -what does that version of .net generate for: complex data structures, char, rpc/enc vs doc/lit, etc.
