This is the third part of the three part series that deals with the issue of faking test data in the context of a legacy app that was built with Microsoft's Entity Framework on top of an MS SQL Server database – an architecture that can be found very often, and that originally came up in the broader context of writing User Acceptance Tests. It shows how you could handle such a scenario with the NDbUnit framework.
This is the second part of the three part series that deals with the issue of faking test data in the context of a legacy app that was built with Microsoft's Entity Framework on top of an MS SQL Server database – an architecture that can be found very often, and that originally came up in the broader context of writing User Acceptance Tests. It shows how you could handle such a scenario with the Typemock Isolator tool.
This is the first of a three part series that deals with the issue of faking test data in the context of a legacy app that was built with Microsoft's Entity Framework on top of an MS SQL Server database – a scenario that can be found very often, and that originally came up in the broader context of writing User Acceptance Tests. It describes a sample application, discusses some general aspects of unit testing in a database context, and also some more specific aspects of the here discussed EF/MSS