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:Error: Bad component name: android.test.InstrumentationTestRunner #624
Comments
From carl.na...@sas.com on October 31, 2013 06:07:10 Reviewing and researching... Owner: carl.na...@sas.com |
From carl.na...@sas.com on October 31, 2013 06:45:21 I see a few things of note:
What may be the problem is that this ADT Bundle was released AFTER RobotiumRC 2013.09.09. I'm venturing a guess the ADT Bundle might include new versions of tools--or different Eclipse versions of tools--that are NOT backward compatible with the normal command-line Android SDK tools we have used before this toolset release. We will have to evaluate the use of the ADT Bundle as a supported mode of command-line driven execution. This part of the log leads me to believe, for example, the am (Activity Manager?) tool usage and api might be different:
What lib jar are you looking at? Cc: lei.w...@sas.com |
From leiwang...@gmail.com on October 31, 2013 20:04:48 I think the problem is the parameter 'instrumentArg' is not correctly assigned, you define it as: This parameter will be used to launch the Instrument by android ADB, In RobotiumRCRelease2013.09.09, two TestRunners have been provided, one is RobotiumTestRunner, the other is SAFSTestRunner. You can use either of them to do the test, but SAFSTestRunner provides more functionality. If you use RobotiumTestRunner, you don't need to provide parameter 'instrumentArg'. RobotiumTestRunner is the default Runner, and 'instrumentArg' has been default assigned as "com.jayway.android.robotium.remotecontrol.client/com.jayway.android.robotium.remotecontrol.client.RobotiumTestRunner" If you want to use SAFSTestRunner, you need to assign 'instrumentArg' as "org.safs.android.engine/org.safs.android.engine.DSAFSTestRunner". One more thing, (suppose RC is installed at C:\robotiumrc) you need to modify the file C:\robotiumrc\SAFSTCPMessenger\local.properties |
From carl.na...@sas.com on November 19, 2013 07:02:21 Status: WontFix |
From bingyuan...@gmail.com on October 30, 2013 22:11:37
What steps will reproduce the problem? 1. I writed a class file,according to example in wiki:
package com.android.test.rc;
import java.util.Properties;
import com.jayway.android.robotium.remotecontrol.solo.Message;
import com.jayway.android.robotium.remotecontrol.solo.SoloTest;
public class MyTest extends SoloTest{
public static final String DEFAULT_AUT_APK = "E:\android\test\NotePad\bin\NotePad.apk";
public static final String messengerApk="C:\robotiumrc\SAFSTCPMessenger\bin\SAFSTCPMessenger-debug.apk";
public static final String testRunnerApk="C:\robotiumrc\RobotiumTestRunner\bin\RobotiumTestRunner-debug.apk";
public static final String instrumentArg="android.test.InstrumentationTestRunner";
public MyTest(){
super();
}
public MyTest(String[] args){
super(args);
}
public MyTest(String messengerApk, String testRunnerApk, String instrumentArg){
super(messengerApk, testRunnerApk, instrumentArg);
}
}
2.run as java application:
Attempting to initialize Android Tools...
C:\Program Files\Android\android-sdk doesn't exist.
Setting Android Tools SDK Dir to E:\android\adt-bundle-windows-x86-20130917\adt-bundle-windows-x86-20130917\sdk
SoloTest INFO: Detected 1 device/emulators attached.
SoloTest DEBUG: INSTALLING E:\android\test\NotePad\bin\NotePad.apk
INSTALLING E:\android\test\NotePad\bin\NotePad.apk
Checking for devices going offline...
Checking 1 for 'offline' status....
No 'offline' devices detected.
ATTEMPTING ADB Install command: adb [Ljava.lang.String;@1a7789c
pkg: /data/local/tmp/NotePad.apk
Success
408 KB/s (65420 bytes in 0.156s)
ADB Install command successful.
SoloTest DEBUG: INSTALLING C:\robotiumrc\SAFSTCPMessenger\bin\SAFSTCPMessenger-debug.apk
INSTALLING C:\robotiumrc\SAFSTCPMessenger\bin\SAFSTCPMessenger-debug.apk
Checking for devices going offline...
Checking 1 for 'offline' status....
No 'offline' devices detected.
ATTEMPTING ADB Install command: adb [Ljava.lang.String;@6db33c
pkg: /data/local/tmp/SAFSTCPMessenger-debug.apk
Success
312 KB/s (34993 bytes in 0.109s)
ADB Install command successful.
SoloTest DEBUG: INSTALLING C:\robotiumrc\RobotiumTestRunner\bin\RobotiumTestRunner-debug.apk
INSTALLING C:\robotiumrc\RobotiumTestRunner\bin\RobotiumTestRunner-debug.apk
Checking for devices going offline...
Checking 1 for 'offline' status....
No 'offline' devices detected.
ATTEMPTING ADB Install command: adb [Ljava.lang.String;@1dafb4e
pkg: /data/local/tmp/RobotiumTestRunner-debug.apk
Success
395 KB/s (126654 bytes in 0.312s)
ADB Install command successful.
LAUNCHING android.test.InstrumentationTestRunner
Checking for devices going offline...
Checking 1 for 'offline' status....
No 'offline' devices detected.
usage: am [subcommand] [options]
usage: am start [-D] [-W] [-P ] [--start-profiler ]
am start: start an Activity. Options are:
am startservice: start a Service. Options are:
am force-stop: force stop everything associated with .
am kill: Kill all processes associated with . Only kills.
processes that are safe to kill -- that is, will not impact the user
experience.
am kill-all: Kill all background processes.
am broadcast: send a broadcast Intent. Options are:
am instrument: start an Instrumentation. Typically this target
is the form <TEST_PACKAGE>/<RUNNER_CLASS>. Options are:
...
Original issue: http://code.google.com/p/robotium/issues/detail?id=545
The text was updated successfully, but these errors were encountered: