This question is locked. New answers and comments are not allowed.
Hello.
We are investigating possibility to use new version of OpenAccess ORM for our new complex project.
We are using unit testing in our development process, and we need to run many unit tests in transaction, which is automatically cancelled after unit test is finished, so we can bring database to initial state, so other unit tests may rely on test data.
Using previous version of OpenAccess ORM and ObjectScope object we was able to call ObjectScope.Transation.Flush() in the middle of unit tests, to generate Identity fields, etc. And then rollback the whole transaction in the end of unit test.
How this can be done with new Domain Model features in Q2 2010?
Thanks,
Alex
We are investigating possibility to use new version of OpenAccess ORM for our new complex project.
We are using unit testing in our development process, and we need to run many unit tests in transaction, which is automatically cancelled after unit test is finished, so we can bring database to initial state, so other unit tests may rely on test data.
Using previous version of OpenAccess ORM and ObjectScope object we was able to call ObjectScope.Transation.Flush() in the middle of unit tests, to generate Identity fields, etc. And then rollback the whole transaction in the end of unit test.
How this can be done with new Domain Model features in Q2 2010?
Thanks,
Alex