Thanks Daniel for pointing out. It was stupid careless simple mistake. Feel shame to bother everyone. Sorry.
On Aug 4, 5:16 am, Daniel Wellman <[email protected]> wrote: > It looks like your method's capitalization is wrong - you want your > method to be called gwtSetUp (with a capital 'u'). If you are using > Java 5 or 6 then using an @Override annotation would have given you a > compiler error, since your gwtSetup method did not override getSetUp. > > Dan > > On Aug 3, 9:08 pm, Art <[email protected]> wrote: > > > By overriding the gwtSetup method (http://google-web- > > toolkit.googlecode.com/svn/javadoc/1.6/index.html?overview- > > summary.html), I tried to do prep before each test execution. However, > > gwtSetup has never been executed before test execution. > > I feel strange that I could not to find any discussion about such > > simple issue anywhere. Is this happening only me? > > > Here's the simple test case as an example: > > package com.appspot.inetools.newsfetcher.client; > > > import com.google.gwt.junit.client.GWTTestCase; > > > /** > > * GWT JUnit tests must extend GWTTestCase. > > */ > > public class ValidaterExecuterTest extends GWTTestCase { > > > /** > > * Must refer to a valid module that sources this class. > > */ > > public String getModuleName() { > > return "com.appspot.inetools.newsfetcher.NewsFetcher"; > > } > > > protected boolean gwtSetupFlag = false; > > protected void gwtSetup() throws Exception { > > super.gwtSetUp(); > > gwtSetupFlag = true; > > //fail( "gwtSetup has been called"); > > } > > > /** > > * Add as many tests as you like. > > */ > > public void testSimple() { > > assertTrue( gwtSetupFlag); > > } > > > } > > > I launch that test by ValidaterExecuterTest-hosted.launch file on > > Eclipse (Galileo or Ganymede). > > Expected it to pass, but it fails. > > > Environment info: > > x86 XP SP 3 > > eclipse.buildId=I20090611-1540 > > (Repro on Ganymede too) > > java.version=1.6.0_13 > > java.vendor=Sun Microsystems Inc. > > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US > > Framework arguments: -product org.eclipse.epp.package.jee.product > > Command-line arguments: -os win32 -ws win32 -arch x86 -product > > org.eclipse.epp.package.jee.product > > GWT 1.7.0 > > JUnit3: plugins\org.junit_3.8.2.v20090203-1005\junit.jar > > > I have been currently working around by putting initialization method > > at the beginning of each tests. It's tedious. I like to avoid it. If > > someone can provide any info about this issue, I highly appreciate it. > > > Regards --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
