Re: Proper Wonder/App Initialization for testing
Re: Proper Wonder/App Initialization for testing
- Subject: Re: Proper Wonder/App Initialization for testing
- From: Mike Schrag <email@hidden>
- Date: Mon, 21 Sep 2009 15:57:00 -0400
initApp is like primeApplication on Wonder steroids ... I actually
need to figure out exactly how to run them from Eclipse. Right now I
run most things using an app wrapper that uses the JUnit console
TestRunner.
On Sep 21, 2009, at 3:13 PM, Chuck Hill wrote:
On Sep 21, 2009, at 8:55 AM, Greg Brown wrote:
Hi,
I converted an app to use Wonder, and I think my tests need do do
something new so that all the Wonder stuff initializes properly.
This page:
http://wiki.objectstyle.org/confluence/display/WONDER/Integrate+Wonder+Into+an+Existing+Application
has nothing about tests ;>o
Unit type tests seem to run fine without initializing the wonder
frameworks, but database type (dbuinit) tests probably need the
wonder stuff to be properly initialized.
ERXExtensions has a bunch of initApp, initEOF, initialize methods,
which one is generally best for testNG / dbuinit initializations?
Or do I need something like an initApp followed by a initEOF?
How do people handle this? a @BeforeSuite annotation to a method
which calls some er.extensions.ERXExtensions.initFoo()?
In an non-Wonder app with similar startup logic, I need to call
WOApplication.primeApplication(). See if that helps.
Chuck
_______________________________________________
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