Hi Mike, Thanks for taking the time to formulate your reply. By using Oracle packages per table, we can get around the stored procedure name limit by using dot notation for our calling convention.  The name limit applies to tables as well. The calling convention could then be : Schema.%pkg_%Table_Name.%Generic CRUD name%   This ...

I'm using MyGeneration with the Trial Product. All my tests worked perfectly with mssql test databases. However, Oracle is our target DB for the current project. It would appear that procedure names cannot exceed 30 characters. Can the Stored procedure template and metadata engine be modified to develop Oracle packages  per table ? Then ...

Mike.Griffin:IIf you code was going to load some data, and the mock data provider didn't return that data, how would your test pass, or would the mock data provider somehow interpret the mock requests and feed back test data? Yes, that's pretty much it. Say I wanted to test my custom code that did some logic on a list of orders for a ...

PurpleFlux: Maybe even the EntitySpaces team would consider making a Test DataProvider that we could programmatically set up and use for tests (probably just really using a dataset or something). Another approach might be to use the MSAccessProvider. Set up an access db with the appropriate data and for each unit test which requires it you could ...

David.Parsons: But, think of the second tier as a combination of Custom+Generated, rather than BLL+DAL. And, do not try to further separate them.   A simple version of another question I've asked (but not yet had answered).  With BLL + DAL, you can unit test the BLL without  referencing a live database (ie, you ...