New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RobotiumRC does not connects and does not starts the tests #537
Comments
From carl.na...@sas.com on May 17, 2013 07:43:34 Don't know how good or bad the entire setup is that you have, but you don't provide any information here as to why the TestRunner on the device/emulator does not launch--or does not launch successfully. Can you review and provide some adb logcat output so that we can see if there is an indication of a problem launching the TestRunner on the device? Status: Incomplete |
From robso...@gmail.com on May 20, 2013 05:58:26 Thank you for your feedback, 05-20 08:46:26.291: D/AndroidRuntime(3653): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<< |
From robso...@gmail.com on May 20, 2013 05:58:26 ...hread.java:4507) In project i'm using 2 externals apklibs.. need some additional configuration? |
From carl.na...@sas.com on May 20, 2013 08:15:13 This is indicative of having the android-support-V4.jar in the TestRunner project when it probably should not be there. If you are testing on Android 4.x platforms then this JAR file should not be used in the APK. The classes it contains already exist on the platform. Additionally, you should be building that TestRunner with the Android SDK libs that already contain those classes. So you would not reference this JAR file in your Android 4.x development projects. The android-support-V4.jar file is only used when testing certain V4 features on Android 2.x and 3.x platforms. Please let us know if removing this JAR file out of your project and APK fixes your problem. Status: Started |
From robso...@gmail.com on May 23, 2013 15:04:27 Hello Robotium team (sorry for the delay), 05-23 16:52:35.653: W/dalvikvm(30506): Class resolved by unexpected DEX: Lcom/test/project/Tela2Activity;(0x4126b360):0x11cda18 ref [Landroid/support/v4/app/FragmentActivity;] Landroid/support/v4/app/FragmentActivity;(0x4126b360):0x131ab38 log from other app test: 05-23 18:14:56.809: W/dalvikvm(4249): Class resolved by unexpected DEX: Lcom/test/project2/view/activity/SplashActivity;(0x4126e410):0x11dde10 ref [Landroid/support/v4/content/LocalBroadcastManager;] Landroid/support/v4/content/LocalBroadcastManager;(0x4126e410):0x11ddcc8 |
From robso...@gmail.com on May 23, 2013 15:04:27 ...alAccessError: Class ref in pre-verified class resolved to unexpected implementation My dependencies (android and support ) in pom.xml:
... and how the new version of Remote Control, have some foresight release? Att, |
From carl.na...@sas.com on May 23, 2013 17:20:14 For V4 apps you need to remove the android-support-v4.jar from the testrunner project. This jar is only used when building and running with pre-v4 sdks and devices. When building with a v4 sdk and running on v4 devices the necessary classes are already included. Let us know when you have tried this and if it resolved your problem. Carl Nagle Status: Incomplete |
From robso...@gmail.com on May 24, 2013 07:31:55 the problem really was it! after two days thinking that the problem was in the app ... but was the support api in RobotiumTestRunner project.. Thank you so much Robotium team.. |
From renasr...@gmail.com on June 15, 2013 19:06:56 Status: Invalid |
From robso...@gmail.com on May 17, 2013 06:27:06
In my project the tests does not starts and time
After instrument and TimeoutException occurs on run test: What steps will reproduce the problem? 1. Instruments the SAFSTCPMessenger and RobotiumTestRunner projects (ant debug)
2. Intall my project and SAFSTCPMessenger and RobotiumTestRunner projects (adb install)
3. Run the test class on JUnit What is the expected output? What do you see instead? Expected to start launch app and run tests.. but not connects! What version of the product are you using? On what operating system? - Win 7 64bits - Intel Core i7 3.4 GHz - 8 GB Ram
SocketProtocol.addListener(): AbstractRunner was successfully registered.
DroidSocketProtocol.addListener(): AbstractRunner was successfully registered.
Port forwarding will be from '2411'
DroidSocketProtocol.createRemoteClientConnection(): Local Runner attempting to make remote Runner connection...
Forwarding port from 'local:2411' to 'device/emulator:2410'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
DroidSocketProtocol.verifyRemoteClient(): Remote client did not verify in timeout period.
DroidSocketProtocol.createRemoteClientConnection(): Remote client did NOT verify itself as a remote SocketProtocolRunner!
Forwarding port from 'local:2411' to 'device/emulator:2410'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
DroidSocketProtocol.verifyRemoteClient(): Remote client did not verify in timeout period.
DroidSocketProtocol.createRemoteClientConnection(): Remote client did NOT verify itself as a remote SocketProtocolRunner!
Forwarding port from 'local:2411' to 'device/emulator:2410'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
DroidSocketProtocol.verifyRemoteClient(): Remote client did not verify in timeout period.
DroidSocketProtocol.createRemoteClientConnection(): Remote client did NOT verify itself as a remote SocketProtocolRunner!
Forwarding port from 'local:2411' to 'device/emulator:2410'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
DroidSocketProtocol.verifyRemoteClient(): Remote client did not verify in timeout period.
DroidSocketProtocol.createRemoteClientConnection(): Remote client did NOT verify itself as a remote SocketProtocolRunner!
Forwarding port from 'local:2411' to 'device/emulator:2410'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
DroidSocketProtocol.verifyRemoteClient(): Remote client did not verify in timeout period.
DroidSocketProtocol.createRemoteClientConnection(): Remote client did NOT verify itself as a remote SocketProtocolRunner!
Forwarding port from 'local:2411' to 'device/emulator:2410'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
DroidSocketProtocol.verifyRemoteClient(): Remote client did not verify in timeout period.
DroidSocketProtocol.createRemoteClientConnection(): Remote client did NOT verify itself as a remote SocketProtocolRunner!
DroidSocketProtocol.createRemoteClientConnection(): The remotePort is set to next possible port number '2412'
DroidSocketProtocol.createRemoteClientConnection(): Local Runner attempting to make remote Runner connection...
Forwarding port from 'local:2411' to 'device/emulator:2412'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
DroidSocketProtocol.verifyRemoteClient(): Remote client did not verify in timeout period.
DroidSocketProtocol.createRemoteClientConnection(): Remote client did NOT verify itself as a remote SocketProtocolRunner!
Forwarding port from 'local:2411' to 'device/emulator:2412'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
DroidSocketProtocol.verifyRemoteClient(): Remote client did not verify in timeout period.
DroidSocketProtocol.createRemoteClientConnection(): Remote client did NOT verify itself as a remote SocketProtocolRunner!
Forwarding port from 'local:2411' to 'device/emulator:2412'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
DroidSocketProtocol.verifyRemoteClient(): Remote client did not verify in timeout period.
DroidSocketProtocol.createRemoteClientConnection(): Remote client did NOT verify itself as a remote SocketProtocolRunner!
Forwarding port from 'local:2411' to 'device/emulator:2412'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
DroidSocketProtocol.verifyRemoteClient(): Remote client did not verify in timeout period.
DroidSocketProtocol.createRemoteClientConnection(): Remote client did NOT verify itself as a remote SocketProtocolRunner!
Forwarding port from 'local:2411' to 'device/emulator:2412'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
DroidSocketProtocol.verifyRemoteClient(): Remote client did not verify in timeout period.
DroidSocketProtocol.createRemoteClientConnection(): Remote client did NOT verify itself as a remote SocketProtocolRunner!
Forwarding port from 'local:2411' to 'device/emulator:2412'
DroidSocketProtocol.createRemoteClientConnection(): Remote Runner seems to be connected!
java.util.concurrent.TimeoutException: waitForRemoteConnected Timeout before Connect
at com.jayway.android.robotium.remotecontrol.solo.SoloRemoteControl.waitForRemoteConnected(SoloRemoteControl.java:502)
at com.jayway.android.robotium.remotecontrol.solo.SoloWorker.initialize(SoloWorker.java:161)
at com.jayway.android.robotium.remotecontrol.solo.SoloTest.initialize(SoloTest.java:532)
at br.fpf.test.cucumber.robotiumrc.CucumberRCTestConfig.startMainLaunch(CucumberRCTestConfig.java:256)
at br.fpf.test.automatedtest.common.cucumber.defaultsteps.TestBase2.startScenario(TestBase2.java:30)
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:597)
at cucumber.runtime.Utils$1.call(Utils.java:42)
at cucumber.runtime.Timeout.timeout(Timeout.java:12)
at cucumber.runtime.Utils.invoke(Utils.java:38)
at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:59)
at cucumber.runtime.Runtime.runHookIfTagsMatch(Runtime.java:192)
at cucumber.runtime.Runtime.runHooks(Runtime.java:184)
at cucumber.runtime.Runtime.runBeforeHooks(Runtime.java:175)
at cucumber.runtime.model.CucumberScenario.run(CucumberScenario.java:35)
at cucumber.runtime.junit.ExecutionUnitRunner.run(ExecutionUnitRunner.java:76)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:65)
at cucumber.runtime.junit.FeatureRunner.runChild(Fea...
Original issue: http://code.google.com/p/robotium/issues/detail?id=458
The text was updated successfully, but these errors were encountered: