Note that there are some explanatory texts on larger screens.

plurals
  1. POError Running NativeDriver with Maven (Software caused connection abort: recv failed)
    primarykey
    data
    text
    <p>I'm trying to use Maven to run NativeDriver Android tests on a continuous integration server (like Hudson). I run the following commands (some names replaced with *):</p> <p>(in Android project)</p> <pre><code>mvn install mvn android:deploy </code></pre> <p>(in NativeDriver test project)</p> <pre><code>adb shell am instrument ***.*****.android3/ com.google.android.testing.nativedriver.server.ServerInstrumentation adb forward tcp:54129 tcp:54129 mvn test </code></pre> <p>I then get the following error:</p> <pre><code>org.openqa.selenium.WebDriverException: java.net.SocketException:Software caused connection abort: recv failed System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_26' Driver info: driver.version: AndroidNativeDriver at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:406) at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:103) at org.openqa.selenium.remote.RemoteWebDriver.&lt;init&gt;(RemoteWebDriver.java:86) at com.google.android.testing.nativedriver.client.AndroidNativeDriver.&lt;init&gt;(UnknownSource) [... many more] </code></pre> <p>In Eclipse, when i run it <a href="https://code.google.com/p/nativedriver/wiki/AndroidMakeAnAppTestable" rel="nofollow">following this guide</a> on my project, everything works like a charm.</p> <p>What is going on? Does Eclipse (with Android plugin) do anything special compared to maven when choosing "Run as -> Android Application"?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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.
 

Querying!

 
Guidance

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