Databases
StackOverflow2013
Postsdbo
POGwtTestWithMockito works from eclipse but not from maven cmdline
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGwtTestWithMockito works from eclipse but not from maven cmdline
    primarykey
    data
    text
    <p>My GwtTestWithMockito derived tests run fine within eclipse.</p> <p>When run from the command-line with maven, every test throws at initialization with the stacktrace below:</p> <pre><code>Forking command line: /bin/sh -c cd /home/mirk/repo/aftd/aftdweb &amp;&amp; /usr/local/java/jdk1.7.0_05/jre/bin/java -Xmx1024M -Xss512M -XX:MaxPermSize=128M org.apache.maven.surefire.booter.ForkedBooter /home/dirk/repo/aftd/aftdweb/target/surefire/surefire2771679869724775356tmp /home/dirk/repo/aftd/aftdweb/target/surefire/surefire_08727036010322995493tmp Running de.telekom.aftd.web.client.presenter.menu.GwtTestWithMockitoCompanyLevelPresenter Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.077 sec &lt;&lt;&lt; FAILURE! initializationError(de.telekom.aftd.web.client.presenter.menu.GwtTestWithMockitoCompanyLevelPresenter) Time elapsed: 0.01 sec &lt;&lt;&lt; ERROR! java.lang.ClassCastException: com.googlecode.gwt.test.internal.junit.GwtBlockJUnit4ClassRunner cannot be cast to org.junit.runner.Runner at com.googlecode.gwt.test.internal.junit.AbstractGwtRunnerFactory.newInstance(AbstractGwtRunnerFactory.java:64) at com.googlecode.gwt.test.internal.junit.AbstractGwtRunnerFactory.create(AbstractGwtRunnerFactory.java:42) at com.googlecode.gwt.test.internal.junit.AbstractGwtRunner.&lt;init&gt;(AbstractGwtRunner.java:31) at com.googlecode.gwt.test.GwtRunner.&lt;init&gt;(GwtRunner.java:19) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31) at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:262) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:158) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95) Results : » ClassCast com.googlecode.gwt.test.internal.junit.GwtBlockJUnit4ClassRunner ... </code></pre> <p>I am using gwt 2.5.0, gwt-test-utils 0.44, mockito-core 1.9.5.</p> <p>I can provide more details, but I am not sure what else would be necessary.</p> <p><strong>Edit:</strong></p> <p>This is the error I get when running them in java-mode in the maven-surefire-plugin. I think it is due to gwt shipping with junit 3, and mockito expecting junit 4.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmirk
    1. USmirk
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POGwtTestWithMockito works from eclipse but not from maven cmdline
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGwtTestWithMockito works from eclipse but not from maven cmdline
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POGwtTestWithMockito works from eclipse but not from maven cmdline
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHave you checked the Maven dependencies using `dependency:tree` to determine if you are pulling in multiple versions of JUnit?
      singulars
      1. POGwtTestWithMockito works from eclipse but not from maven cmdline
      1. USPeter Mularien
    2. CO@Peter Mularien: No, and I can only do this tomorrow morning from my desk. I seem to remember that gwt comes with its own built-in Junit 3. I pull in junit 4.10 in the maven dependencies. Maybe I should stick ti the one provided by gwt?
      singulars
      1. POGwtTestWithMockito works from eclipse but not from maven cmdline
      1. USmirk
    3. COI only include a single junit version 4.10. I assume that I clash with some internal gwt junit version. I still have no idea about a solution?
      singulars
      1. POGwtTestWithMockito works from eclipse but not from maven cmdline
      1. USmirk
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload