I think it really depends on the purpose of the test, I don't think hitting the disk is all that bad for an integration test. Of course if you hit the disk in all your tests and you have a whole bunch of them your build time will get unreasonable, but as long as it's for a fairly small set of tests you should be fine.
On Feb 4, 8:35 am, HP <[email protected]> wrote: > Thanks guys > > Tim certainly is right about not hitting the disk, but I've got > another idea to avoid it - a method that would get the object on > runtime, examine it by reflection and return the code to create a mock > of it, ready to paste to the unit test - including the data insertion. > Are there such things in this world? > > greets > hp --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/RhinoMocks?hl=en -~----------~----~----~----~------~----~------~--~---
