I've just seen that: "Additionally, correct tests can sometimes fail on HtmlUnit, either because the HtmlUnit support for that feature is lacking or because of HtmlUnit's issues with flakiness when running asynchronous tests."
Is this timeout / no response one of the types of flakiness that might be expected? Does this statement only apply where my tests are asynchronous (i.e. with a Timer?) The tests run easily within the timeout when run from the plug-in I've seen various similar bug reports but nothing that exactly matches: http://www.google.co.uk/search?hl=en&lr=&ei=LetFS5z2Lciu4Qac4832Ag&sa=X&oi=spell&resnum=0&ct=result&cd=1&ved=0CA0QBSgA&q=gwt+%22responded+back+to+JUnitShell%22&spell=1 The thing is that I don't have an intermittent problem - it always fails. On Jan 6, 4:00 pm, Jon Vaughan <jsvaug...@gmail.com> wrote: > Hi, > > I recently upgraded to GWT 2 from 1.5.x. My tests, for some reason, > are now failing when I run them from Ant: > > run-gwt-tests: > [junit] WARNING: multiple versions of ant detected in path for > junit > [junit] jar:file:/C:/Program%20Files/eclipse/plugins/ > org.apache.ant_1.7.1.v20090120-1145/lib/ant.jar!/org/apache/tools/ant/ > Project.class > [junit] and jar:file:/C:/_code/bionicbooks/lib/build-Windows/ > gwt-dev-2.0.0.jar!/org/apache/tools/ant/Project.class > [junit] Running > com.monksvaughan.accounts.test.ui.JUnitDropDownControls > [junit] - 1 client(s) haven't responded back to JUnitShell since > the start of the test. > [junit] Actual time elapsed: 60.035 seconds. > [junit] ) > > BUILD FAILED > > When I run the same test using the GWT eclipse plugin, it works > without a problem. My Junit task is very simple: > > <target name="run-gwt-tests"> > <mkdir dir="${build}/testresults" /> > <junit printsummary="yes" haltonfailure="yes" fork="true"> > <classpath refid="test.class.path" /> > <formatter type="xml"/> > <batchtest todir="${build}/testresults"> > <fileset dir="${test}"> > <include name="**/ui/JUnit*.java"/> > </fileset> > </batchtest> > <jvmarg value="-Xmx512m" /> > </junit> > </target> > > So presumably this is a classpath problem. The testing doc (http:// > code.google.com/webtoolkit/doc/latest/DevGuideTesting.html) says it > should include: > > Your project's src directory > Your project's bin directory > The gwt-user.jar library > The gwt-dev.jar library > The junit.jar library > > Which my "test.class.path" includes (I have double checked with -v) > > Anybody have any ideas or seen something similar? It's not the 2 Ant > versions is it? I am currently using Junit 3.8.1 rather than JUnit 4, > but presumably that isn't the issue either. Thoughts gratefully > received. > > Jon
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
