• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs


  • Subject: Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs
  • From: "M.Y. Tjoe" <email@hidden>
  • Date: Mon, 14 Dec 2009 17:05:45 +1100

Hi all,

Anybody has any update on this issues? I am the next lucky winner for this one. I've updated to the latest Wonder library (2009-08-20) and using the latest Juint (4.8.1) but still have this problem. Tried ERXTestCase but that doesn't work for me. My test would not run at all which is good I guess. Also, I am using ERXMemoryAdaptor in the model so I don't know if this is not supported. Any help would be much appreciated.

Regards,
Harvey


On 13/12/2009, at 1:41 AM, Q wrote:


On 11/12/2009, at 6:34 PM, Paul Hoadley wrote:

On 11/12/2009, at 4:41 PM, Q wrote:

I ran into this recently too. It seemed to resolve itself after I did the following:

1. Update wonder
2. Ensure all tests classes that use EOF inherit from ERXTestCase

I'm somewhat of a JUnit novice: wouldn't that result in mixing the JUnit3 and JUnit4 APIs? ERXTestCase extends junit.framework.TestCase which has the old prescribed method names like setUp(). I'm trying to work to JUnit4, using the @Before, @BeforeClass, @Test annotations, and so on. Or doesn't it matter?



The actual inheritance isn't really that important, only that Wonder / EOF is initialised correctly, which ERXTestCase does for you.


3. Add the framework to a test app (the tests were part of a framework)
4. Create a run configuration for the tests that runs from the test app's build folder


The problem I was having seemed to stem from the model somehow being unsuccessfully loaded twice, how this happened, or why the failures were unpredictable I didn't have the time to determine.

Thanks Q, I'll try this out.


-- Paul.

w  http://logicsquad.net/
h  http://paul.hoadley.name/





-- Seeya...Q

Quinton Dolan - email@hidden
Gold Coast, QLD, Australia (GMT+10)




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@uow.edu.au


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
  • Follow-Ups:
    • Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs
      • From: Paul Hoadley <email@hidden>
References: 
 >JUnit4 testing of EOs: InvocationTargetException on subsequent runs (From: Paul Hoadley <email@hidden>)
 >Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs (From: Paul Hoadley <email@hidden>)
 >Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs (From: Mike Schrag <email@hidden>)
 >Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs (From: Paul Hoadley <email@hidden>)
 >Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs (From: Q <email@hidden>)
 >Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs (From: Paul Hoadley <email@hidden>)
 >Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs (From: Q <email@hidden>)

  • Prev by Date: Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs
  • Next by Date: Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs
  • Previous by thread: Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs
  • Next by thread: Re: JUnit4 testing of EOs: InvocationTargetException on subsequent runs
  • Index(es):
    • Date
    • Thread