• 首先用SIKULI IDE 打开脚本,然后按以下格式进行调整

• 然后单击FILE-EXPORT Executable 命令导出.skl格式的文件.
• 打开命令行窗口,并定位到SIKULI IDE的安装目录,然后执行以下命令来运行脚本和输出结果

• 等整个测试执行完毕后,你可以从log文件中看到以下信息

转自 http://www.13com.net/article/article.asp?articleid=1041

在开发Android程序的时候，我们往往需要处理来电或者短消息，但是在开发过程中基本都是通过模拟器来进行调试，那么下面我们就介绍一下如何向模拟器打电话和发短信。

首先在Eclipse中点击菜单Windows->Open perspective->DDMS进入DDMS视图：

然后在DDMS视图的Emulator Control视窗中，Incoming number框内填入电话号码(随便填)，选择Voice，然后点击Call按钮。

模拟器上即可显示来自Incoming number的电话呼叫。

然后在Emulator Tools中选择SMS，并填写短消息内容，然后点击Send按钮。

相应的模拟器上就会收到来自Incoming number发送的该短消息。

当然，如果觉得这个方法太麻烦，也可以用命令行的方式来完成上述操作，先通过命令行telnet localhost 5554，进入Android Console，然后就可以使用命令进行一些操作，拨打电话和发送短消息是使用gsm和sms命令。gsm和sms两个命令的参数如下：

完成上述一个电话呼叫和短信的完整命令是：

在使用SELENIUM RC进行测试时,总是会发现在打开网页的过程中TIMEOUT 30000MS的错误提示.

这是因为打开网页时有一个默认的超时限制,更改这个默认值的命令是:

selenium.set_timeout("60000")

这个值最好是放在SetUP方法中.

Some comments:

• You don't need a wait_for_page_to_load after an open, that will cause you timeouts because once the page is loaded after the opeen, it will start waiting again and the page will not be loading.
• Most of the failures you get from selenium (timeouts, object not found) can be caught with try-except statements
• You should set the timeout in your tests withing the test itself (using set_timeout), that way it doesn't depend on the way you start the server, it will always wait the time you wanted

在使用SELENIUM RC进行测试时,总是会发现在打开网页的过程中TIMEOUT 30000MS的错误提示.

这是因为打开网页时有一个默认的超时限制,更改这个默认值的命令是:

selenium.set_timeout("60000")

这个值最好是放在SetUP方法中.

Some comments:

• You don't need a wait_for_page_to_load after an open, that will cause you timeouts because once the page is loaded after the opeen, it will start waiting again and the page will not be loading.
• Most of the failures you get from selenium (timeouts, object not found) can be caught with try-except statements
• You should set the timeout in your tests withing the test itself (using set_timeout), that way it doesn't depend on the way you start the server, it will always wait the time you wanted

   Deleting Temporary Files Painlessly

http://www.hardwarehell.com/articles/bootclean.shtml

See Addendum  for Windows XP, ME and 2000

This article is not intended to be a DOS lesson or tutorial, but to show you a simple and painless way that I help keep my drive free from useless file clutter. There are other command variations to do this, however, this is what I have found to work best for me. This article assumes that you already have a basic knowledge of DOS commands, the autoexec.bat file and the consequences of typos and the incorrect use of wildcards.

The temporary internet files folder, history folder and cookies folder contain a file called index.dat. Windows uses index.dat to keep a coded record of the files in the folder where it resides. Windows will NOT let you delete index.dat! If you delete the files in these folders through any Windows method, you are still left with the index.dat containing all the info you thought you just deleted. So much for deleting your tracks! This file can become completely bloated, not to mention corrupted, since it won't match the actual files in the folder. The index.dat file can only be deleted in DOS and are included in your cleanup using the DELTREE command.

All modifications are done in the autoexec.bat file. This is my preference so that these files are deleted each time I boot. The autoexec.bat file is not required after Windows 3.1. If you do not have this file in the root directory of your C:\ drive, just create it in Notepad (make sure that the "Word Wrap" option is OFF) and save as autoexec.bat. The file could actually be saved as "whatever_you_want_to_name.bat" file, but would have to be ran manually and in DOS mode. (Not a DOS window)

If I ever use Netscape, (far and few between) I have the cache files directed to my C:\Windows\Temporary Internet Files location rather than adding yet another directory to clean. If you use a Netscape browser, your cache files may be in the default location at: C:\Program Files\Netscape\users\username\cache (or whatever drive Netscape is installed) Just add another DELTREE line with the path where they can be found.

Here is a copy of my autoexec.bat file with explanation of the commands below. The grayed out lines are what existed before I added the cleanup routine. (Yes, I know neither is necessary, but I have my own reasons) Make sure you change any paths where your files may be kept in different folders than mine and delete out any lines of folders you decide not to have cleaned up.

"my" autoexec.bat File

@ECHO OFF
rem - By Windows Setup - c:\windows\command\mscdex.exe /D:aspicd0 /M:12 /L:I
PATH=%PATH%;
if exist c:\windows\smartdrv.exe c:\windows\smartdrv.exe 2048 16
DELTREE /y c:\windows\history\*.* > NUL
DELTREE /y c:\windows\tempor~1\*.* > NUL
DELTREE /y c:\windows\temp\*.* > NUL
DELTREE /y c:\windows\cookies\*.* > NUL
DELTREE /y c:\windows\applic~1\micros~1\office\recent\*.* > NUL
DELTREE /y c:\windows\ShellIconCache
if exist del c:\windows\ff*.tmp
if exist del c:\windows\system\advert.dll

Explanations of autoexec.bat commands

@ECHO OFF suppresses the "command" from displaying on the screen. Normally, when commands are executed from a batch file, they are displayed on the screen.  

if exist is a conditional command that says if the file exists, load it. If it does not exist, no big deal, no error message and the command is ignored.

smartdrv.exe is a standard disk cache used to speed things up. It's not needed for Windows, like the old days, but sure speeds things up in DOS. Parameters are the amount of memory in Kb to use.

DELTREE allows you to delete a directory even if it contains files and subdirectories or has hidden, system or read-only attributes. 

/Y Suppresses a prompt to confirm the deletion.

*.*  delete all the files and subdirectories but leave the directory itself. This saves adding an additional command line to recreate the folder. 

> NUL instruction disables output to the screen as your computer boots. Without it, error messages about "files not found" and a file by file line as each file is being deleted.. If a folder is already empty, you would also get an error message. If you would like to see exactly what is going on, just delete the > NUL part.

ShellIconCache is a hidden file in the Windows directory that stores icon cache files. Just like the temporary internet files folder, it becomes very unproductive when the file gets too big. This file can become very bloated and corrupted. (example: black, odd looking icons) If it doesn't seem to work, try replacing ShellIconCache with shelli~1.

if exist del c:\windows\ ff*.tmp deletes garbage files that Office leaves behind, if they exist.

if exist del c:\windows\system\ advert.dll deletes the spyware file (advert.dll) that many demo programs install with their program. This file is always secretly loaded and running on your system. It reports ALL of your online activities back to the originator.

NOTE: Some program installations that require a reboot, may be using the temp folder to store files needed to complete installation upon the reboot. (98lite is one) If so, just put a REM before the DELTREE /y c:\windows\temp\*.* > NUL line. After the installation, go back and remove the REM.

See Addendum  for Windows XP, ME and 2000

Also, we have a great thread going on the subject here. A lot is covered here that I keep seeing in the same emails again and again.

Reader Andy, pointed out another line to add, that I hadn't since I have these files deleted on shutdown with a registry tweak. Thanks, Andy.

DELTREE /y c:\windows\recent\*.* > NUL

Reader Robert adds, "There is another [I think better] way to keep your Netscape cache clear, and speed up Netscape in the process. I set my disk cache to 0 bytes, and memory cache to 4096 kilobytes, and have been running like that for years."

Reader Eric offers his method of removing index.dat files in Win9x.

If you want a quick & easy way to keep your cookies, cache, & history files & those annoying MS index.dat files cleaned up here's a very simply way to do it. I created a RAMDrive using MS DOS RAMDrive.sys. Then I changed the pointers in the registery to point to the RAMDrive & saved cache, cookies, & history junk files there. Now everytime you reboot poof they are gone.

Click on Start...Run...sysedit
Select Config.sys

Copy & paste the following into your config.sys

<--------Begin copy here-------->

DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
DOS=HIGH,UMB
DEVICEhigh=C:\WINDOWS\RAMdrive.sys 5120 /E

<--------End copy here-------->

You can change the 5120 to what ever amount of RAM you want to steal. I have 320M RAM so I took 5M. Under Internet Options You could also lower Amount of disk space used for Temp Internet Files to 1 or 2M.

1024 1M RAM
2048 2M RAM
3072 3M RAM
4096 4M RAM
5120 5M RAM
6144 6M RAM
7168 7M RAM

Reboot before editing the registery so you can now see your RAMDrive:
Using regedit go to this Key & set the following:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders

Cache "Enter RAMDrive Letter" ex: F:
Cookies "Enter RAMDrive Letter" ex: F:
History "Enter RAMDrive Letter" ex: F:

Reader Steve gives his method of index.dat cleanup on a network when your index.dat file is stored on the server when  you log out.

Android Market on Emulator （http://doll.javaeye.com/blog/605969）

转自:http://hewei1107.blog.163.com/blog/static/1275671372009910101747758/

AVD quickview

• You need to create an AVD to run any app in the Android emulator
• Each AVD is a completely independent virtual device, with its own hardware options, system image, and data storage.
• You create AVD configurations to model different device environments in the Android emulator.

In this document

1. Creating an AVD
   1. Listing targets
   2. Selecting a target
   3. Creating the AVD
   4. Setting hardware emulation options
   5. Default location of the AVD files
2. Managing AVDs
   1. Moving an AVD
   2. Updating an AVD
   3. Deleting an AVD
3. Command-line options

See Also

1. Android Emulator

Android Virtual Devices (AVDs) are configurations of emulator options that let you better model an actual device.

Each AVD is made up of:

• A hardware profile.  You can set options to define the hardware features of the virtual device. For example, you can define whether the device has a camera, whether it uses a physical QWERTY keyboard or a dialing pad, how much memory it has, and so on.
• A mapping to a system image.  You can define what version of the Android platform. will run on the virtual device. You can choose a version of the standard Android platform. or the system image packaged with an SDK add-on.
• Other options.  You can specify the emulator skin you want to use with the AVD, which lets you control the screen dimensions, appearance, and so on. You can also specify the emulated SD card to use with the AVD.
• A dedicated storage area on your development machine, in which is stored the device's user data (installed applications, settings, and so on) and emulated SD card.

You can create as many AVDs as you need, based on the types of devices you want to model and the Android platforms and external libraries you want to run your application on.

In addition to the options in an AVD configuration, you can also specify emulator command-line options at launch or by using the emulator console to change behaviors or characteristics at run time. For a complete reference of emulator options, please see the Emulatordocumentation.

To create and manage AVDs, you use the android tool provided in the Android SDK. For more information about how to work with AVDs from inside your development environment, see Developing in Eclipse with ADT or Developing in Other IDEs, as appropriate for your environment.

Creating an AVD

The Android SDK does not include any preconfigured AVDs, so you need to create an AVD before you can run any application in the emulator (even the Hello World application).

To create an AVD, you use the android tool, a command-line utility available in the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; "><sdk>/tools/</COde> directory. Managing AVDs is one of the two main function of the android tool (the other is creating and updating Android projects). Open a terminal window and change to the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; "><sdk>/tools/</COde>directory, if needed

To create each AVD, you issue the command <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">android create avd</COde>, with options that specify a name for the new AVD and the system image you want to run on the emulator when the AVD is invoked. You can specify other options on the command line also, such as to create an emulated SD card for the new AVD, set the emulator skin to use, or set a custom location for the AVD's files.

Here's the command-line usage for creating an AVD:

android create avd -n <name> -t <targetID> [-<option> <value>] ...

You can use any name you want for the AVD, but since you are likely to be creating multiple AVDs, you should choose a name that lets you recognize the general characteristics offered by the AVD.

As shown in the usage above, you must use the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">-t</COde> (or <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">--target</COde>) argument when creating a new AVD. The argument sets up a mapping between the AVD and the system image that you want to use whenever the AVD is invoked. You can specify any Android system image that is available in your local SDK — it can be the system image of a standard Android platform. version or that of any SDK add-on. Later, when applications use the AVD, they'll be running on the system that you specify in the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">-t</COde> argument.

To specify the system image to use, you refer to its target ID — an integer — as assigned by the android tool. The target ID is not derived from the system image name, version, or API Level, or other attribute, so you need to have the android tool list the available system images and the target ID of each, as described in the next section. You should do this before you run the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">android create avd</COde> command.

Listing targets

To generate a list of system image targets, use this command:

android list targets

The android tool scans the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; "><sdk>/platforms</COde> and <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; "><sdk>/add-ons</COde> directories looking for valid system images and then generates the list of targets. Here's an example of the command output:

Available Android targets:id:1    Name: Android 1.1    Type: platform    API level: 2    Skins: HVGA (default), HVGA-L, HVGA-P, QVGA-L, QVGA-Pid:2    Name: Android 1.5    Type: platform    API level: 3    Skins: HVGA (default), HVGA-L, HVGA-P, QVGA-L, QVGA-Pid:3    Name: Google APIs    Type: add-on    Vendor: Google Inc.    Description: Android + Google APIs    Based on Android 1.5 (API level 3)    Libraries:    * com.google.android.maps (maps.jar)        API for Google Maps    Skins: HVGA (default), HVGA-L, QVGA-P, HVGA-P, QVGA-L

Selecting a target

Once you have generated the list of targets available, you can look at the characteristics of each system image — name, API Level, external libraries, and so on — and determine which target is appropriate for the new AVD.

Keep these points in mind when you are selecting a system image target for your AVD:

• The API Level of the target is important, because your application will not be able to run on a system image whose API Level is less than that required by your application, as specified in the<COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">minSdkVersion</COde> attribute of the application's manifest file. For more information about the relationship between system API Level and application <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">minSdkVersion</COde>, see Specifying Minimum System API Version.
• Creating at least one AVD that uses a target whose API Level is greater than that required by your application is strongly encouraged, because it allows you to test the forward-compatibility of your application. Forward-compatibility testing ensures that, when users who have downloaded your application receive a system update, your application will continue to function normally.
• If your application declares a <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">uses-library</COde> element in its manifest file, the application can only run on a system image in which that external library is present. If you want your application to run on the AVD you are creating, check the application's <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">uses-library</COde> element and select a system image target that includes that library.

Creating the AVD

When you've selected the target you want to use and made a note of its ID, use the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">android create avd</COde> command to create the AVD, supplying the target ID as the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">-t</COde> argument. Here's an example that creates an AVD with name "my_android1.5" and target ID "2" (the standard Android 1.5 system image in the list above):

android create avd -n my_android1.5 -t 2

If the target you selected was a standard Android system image ("Type: platform"), the android tool next asks you whether you want to create a custom hardware profile.

Android 1.5 is a basic Android platform.Do you wish to create a custom hardware profile [no]

If you want to set custom hardware emulation options for the AVD, enter "yes" and set values as needed. If you want to use the default hardware emulation options for the AVD, just press the return key (the default is "no"). The android tool creates the AVD with name and system image mapping you requested, with the options you specified.

If you are creating an AVD whose target is an SDK add-on, the android tool does not allow you to set hardware emulation options. It assumes that the provider of the add-on has set emulation options appropriately for the device that the add-on is modeling, and so prevents you from resetting the options.

For a list of options you can use in the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">android create avd</COde> command, see the table in Command-line options for AVDs, at the bottom of this page.

Setting hardware emulation options

When are creating a new AVD that uses a standard Android system image ("Type: platform"), the android tool lets you set hardware emulation options for virtual device. The table below lists the options available and the default values, as well as the names of properties that store the emulated hardware options in the AVD's configuration file (the config.ini file in the AVD's local directory).

Default location of the AVD files

When you create an AVD, the android tool creates a dedicated directory for it on your development computer. The directory contains the AVD configuration file, the user data image and SD card image (if available), and any other files associated with the device. Note that the directory does not contain a system image — instead, the AVD configuration file contains a mapping to the system image, which it loads when the AVD is launched.

The android tool also creates a <AVD name>.ini file for the AVD at the root of the .android/avd directory on your computer. The file specifies the location of the AVD directory and always remains at the root the .android directory.

By default, the android tool creates the AVD directory inside <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">~/.android/avd/</COde> (on Linux/Mac), <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">C:\Documents and Settings\<user>\.android\</COde> on Windows XP, and<COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">C:\Users\<user>\.android\</COde> on Windows Vista. If you want to use a custom location for the AVD directory, you can do so by using the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">-p <path></COde> option when you create the AVD:

android create avd -n my_android1.5 -t 2 -p path/to/my/avd

If the .android directory is hosted on a network drive, we recommend using the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">-p</COde> option to place the AVD directory in another location. The AVD's .ini file remains in the .android directory on the network drive, regardless of the location of the AVD directory.

Managing AVDs

The sections below provide more information about how to manage AVDs once you've created them.

Moving an AVD

If you want to move or rename an AVD, you can do so using this command:

android move avd -n <name> [-<option> <value>] ...

The options for this command are listed in Command-line options for AVDs at the bottom of this page.

Updating an AVD

If, for any reason, the platform/add-on root folder has its name changed (maybe because the user has installed an update of the platform/add-on) then the AVD will not be able to load the system image that it is mapped to. In this case, the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">android list targets</COde> command will produce this output:

The following Android Virtual Devices could not be loaded: Name: foo Path: <path>/.android/avd/foo.avd Error: Invalid value in image.sysdir. Run 'android update avd -n foo'

To fix this error, use the <COde style="color: rgb(0, 112, 0); font-family: monospace; line-height: 1em; ">android update avd</COde> command to recompute the path to the system images.

Deleting an AVD

You can use the android tool to delete an AVD. Here is the command usage:

android delete avd -n <name>

When you issue the command, the android tool looks for an AVD matching the specified name deletes the AVD's directory and files.

Command-line options for AVDs

The table below lists the command-line options you can use with the android tool.

转自：http://rayleung.javaeye.com/blog/480908

Android adb的使用略解

安卓网的一个帖子，写得不错，记下来

ADB全称Android Debug Bridge, 是android sdk里的一个工具, 用这个工具可以直接操作管理android模拟器或者真实的andriod设备(如G1手机).

它的主要功能有:

• 运行设备的shell(命令行)
• 管理模拟器或设备的端口映射
• 计算机和设备之间上传/下载文件
• 将本地apk软件安装至模拟器或android设备

ADB是一个 客户端-服务器端 程序, 其中客户端是你用来操作的电脑, 服务器端是android设备.

先说安装方法, 电脑上需要安装客户端. 客户端包含在sdk里. 设备上不需要安装, 只需要在手机上打开选项settings-applications-development-USBdebugging.

对于Mac和Linux用户, 下载好的sdk解压后, 可以放~或者任意目录. 然后修改~/.bash_profile文件, 设置运行环境指向sdk的tools目录.
具体是打开~/.bash_profile文件(如果没有此文件也可以自行添加), 在里面加入一行:

export PATH=${PATH}:<你的sdk目录>/tools

然后就可以使用adb命令了.

嫌安装麻烦的同学其实也可以省去上面安装步骤, 直接输入完整路径来使用命令
对于windows xp用户, 需要先安装usb驱动  android_usb_windows.zip (1.33 MB) , 然后如果你只打算使用adb而不想下载整个sdk的话, 可以下载这个单独的adb工具包  adb_win.zip (571.56 KB) 下载后解压, 把里面 adb.exe 和 AdbWinApi.dll 两个文件放到系统盘的 windows/system32 文件夹里就可以了

ADB常用的几个命令
1. 查看设备

• adb devices

这个命令是查看当前连接的设备, 连接到计算机的android设备或者模拟器将会列出显示

2. 安装软件

• adb install <apk文件路径>

这个命令将指定的apk文件安装到设备上

3. 卸载软件

• adb uninstall <软件名>
• adb uninstall -k <软件名>

如果加 -k 参数,为卸载软件但是保留配置和缓存文件.

4. 登录设备shell

• adb shell
• adb shell <command命令>

这个命令将登录设备的shell.
后面加<command命令>将是直接运行设备命令, 相当于执行远程命令

5. 从电脑上发送文件到设备

• adb push <本地路径> <远程路径>

用push命令可以把本机电脑上的文件或者文件夹复制到设备(手机)

6. 从设备上下载文件到电脑

• adb pull <远程路径> <本地路径>

用pull命令可以把设备(手机)上的文件或者文件夹复制到本机电脑

7. 显示帮助信息

• adb help

这个命令将显示帮助信息

1. Original vnc project

http://code.google.com/p/android-vnc/

This one could not be used on G1, because it need build a special keyboard driver into kernel

2. Forked vnc server

http://code.google.com/p/android-vnc-server/

Forked from android-vnc project on google code.

The original android-vnc need build a special keyboard driver into kernel. It's not necessary. Also the touch event support is added in this version.

First download and install the binary

 http://code.google.com/p/android-vnc-server/downloads/list

If you have adb on server:

#adb push androidvncserver /data 
#adb shell /data/androidvncserver

Or you can just copy the downloaded file androidvncserver to the /sdcard, 

Then umount the sdcard and launch the terminal from your G1, then type

# su    <-  I have root access, I'm not sure whether the following steps work without root access.

# cp /sdcard/androidvncserver /data/

# chmod a+x /data/androidvncserver

# /data/androidvncserver &

And finally: 

Run vnc viewer from hose PC.

Here I use

http://downloads.sourceforge.net/vnc...3.10-setup.exe 

make sure the connection address with port 5901 : 192.168.0.101:5901

Now, I can remote control my phone from host pc.

在安装的过程上，遇到了以下问题， 在使用chmod命令时，总是提示，permission denied,在chmod 命令后添加了权限 777（即可执行又可读写的权限） 就可以了。

另附图：通过 ADB启动VNC SERVER时的图

Google has released the Android 2.0 SDK as of October 27th, 2009. We know how eager everyone has been to get their hands on Android 2.0, so we have decided to write up instructions so that anyone may download and install the SDK, then create and run an emulator instance.

Note, the emulator is not intended to duplicate any particular device, so treat this more as a look at some of the core new features of Android 2.0 than an emulation of any current or future device. Also, things that require hardware features are not available in the emulator. No multi-touch in here guys (unless you manage to get two mice to work?).

Enough of the talk, let’s get down to business.

1)      Download appropriate file for your system from http://developer.android.com/sdk/index.html

http://code.google.com/android/download.html

2)      Extract to desired location

3)      Run “SDK Setup.exe” (or the equivalent for your system)

Launch sdksetup.ext

a.       If you receive an error message stating “Failed to fetch url…” then you will have to force the Setup program to use http in lieu of https.

Got this error? Follow the steps.

i.      Close the “Refresh Sources” window

ii.      Cancel the “Choose Packages to Install” window

iii.      Select “Settings” from the left side of the “Android SDK and AVD Manager” window

iv.      Check the box labeled “Force https://… sources to be fetched using http://…”

v.      Click “Save and Apply”

vi.      Close and restart the SDK Setup program

4)      Choose the packages that you wish install

Select only the packages you need.

a.       If you are only interested in trying out the Android 2.0 Emulator

i.      Reject everything except “SDK Platform. Android 2.0. API 5, revision 1” by selecting each item then selecting the Reject option

b.      If you plan to develop Android applications and Games, you may wish to Accept All

c.       Click “Install Selected”

5)      Allow the selected packages to download and install then close the “Installing Archives” window

6)      Create a new Android Virtual Device (AVD)

These are the settings to emulate the Moto Droid.

a.       Select “Virtual Devices” from the left side of the “Android SDK and AVD Manager” window

i.      Click “New”

ii.      Enter a Name

iii.      Choose a Target

iv.      Enter a size for the emulated SD Card

v.      Choose a Skin

1.      To emulate current hardware such as the G1, MyTouch 3G, Hero, etc…

a.       Leave the default value

2.      To emulate the Motorola Droid

a.       Choose WVGA 854

3.      To emulate other devices

a.       Choose anything else

vi.      Click “Create AVD”

7)      Start your newly created Virtual Device

A successfully created AVD.

a.       Choose the Virtual Device from the list

b.      Click “Start…”

c.       Click “Launch”

Just click launch.

8)      Allow copious time for Emulator to start up

First startup will take a few minutes.

9)      Enjoy!

• 在所有的机器(比如GRID机,RC机)上,都必须要安装ANT和SELENIUM GRID
  
• 必须在GRID机上先启动 ant-hub,然后再在其它的机器上启动RC,这样在localhost:4444/console中,你才能看到available remote control的信息.
• 如果在某台机器上想用某种浏览器(e.g.safari)进行测试,那在在这台机器上,必须将支持此浏览器的RC启动起来,格式如下:ant -Dport=5556 -Dhost=192.168.1.4 -DhubURL=http://192.168.1.70:4444 -Denvironment="Safari on Windows" launch-remote-control

• ant launch-hub

• Launch a remote control(in the other machine or in the same machine) declaring that it provides the Safari environment: ant -Dport= -Dhost= -DhubURL= -Denvironment="*safari" launch-remote-control

• Launch the other remote controls the same way:

• ant -Denvironment="*safari" -Dport=5556 launch-remote-control
  ant -Denvironment="*safari" -Dport=5557 launch-remote-control

• Launch the demo overriding the browser system property:
• ant -Dbrowser="*safari" run-demo-in-parallel