I think Johan is right. Unfortunately I'm not able to look into it over the weekend since my computer broke down yesterday and I won't get it fixed before Tuesday next week.
I haven't maintained the example testcases for a while due to various problem with jwebunit, javascript, etc. The whole concept didn't seem to be very well suitable for testing. None of the tests in examples evolved beyond very simple button clicks. Does Bamboo run the example tests as well? If yes, than the exception may be due to some other changes. Please bare also in mind that some test related code must be replicated (sync) with examples, since it is not part of core (src/java). Juergen On 4/7/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
looks more like a testcase failure itself to me. Shouldn't the test case make the application and set in in the thread local before it does a call that want to construct wicket things? johan On 4/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > There's a testing failing in Wicket examples currently. Is that due to > the recent refactorings? > > Stacktrace: > > wicket.WicketRuntimeException: There is no application attached to > current thread main > at wicket.Application.get(Application.java:167) > at > wicket.util.resource.locator.ResourceStreamLocator.locateByResourceFinder( > ResourceStreamLocator.java:196) > at wicket.util.resource.locator.ResourceStreamLocator.locate( > ResourceStreamLocator.java:131) > at wicket.util.resource.locator.ResourceStreamLocator.locate( > ResourceStreamLocator.java:106) > at wicket.examples.hangman.WordGenerator.<init>(WordGenerator.java > :56) > at wicket.examples.hangman.WordGeneratorTest.testWordGenerator( > WordGeneratorTest.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) > at junit.extensions.TestSetup$1.protect(TestSetup.java:19) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.extensions.TestSetup.run(TestSetup.java:23) > at > org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run( > JUnit3TestReference.java:130) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run( > TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests > (RemoteTestRunner.java:460) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests > (RemoteTestRunner.java:673) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run( > RemoteTestRunner.java:386) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( > RemoteTestRunner.java:196) > > Eelco >
