Re: EOEditingContext for JUnit
Re: EOEditingContext for JUnit
- Subject: Re: EOEditingContext for JUnit
- From: Mike Schrag <email@hidden>
- Date: Mon, 24 Mar 2008 15:16:10 -0400
You can try using the JavaMemoryAdaptor from Wonder ... It's an
implementation of the adaptor layer in-memory, so to an EC it looks
completely "real" but it's actually just writing EO's into
NSDictionaries internally. Really handy for test cases. We use this
in the new examples in AjaxExample.app. I think there's still a bug
that it doesn't properly impl support for inheritance at the moment,
though (just hadn't gotten around to looking into the reason).
ms
On Mar 24, 2008, at 3:13 PM, Chris Meyer wrote:
I'm writing JUnit tests and I'm trying to add a test for a 'clone'
problem. Unfortunately, the mockEditingContext() included with
wounittest2 framework doesn't seem to have enough functionality to
reproduce the bug.
Is there a way to create a new editing context connected to an
object store connected to a REAL database configured for testing?
If so, how would I go about it in a JUnit test?
Is there existing code to do something similar that I can look at?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden