Appium服务器如何开启？ (appium怎么开启服务器)
Appium是当今市场上非常受欢迎的跨平台自动化测试工具，可以通过它来执行针对手机、平板电脑和桌面应用程序的自动化测试。要开始使用Appium测试，必须首先启动一个Appium服务器。本文将介绍如何开启Appium服务器。
1. 安装Node.js和NPM
要安装Appium，请先安装Node.js和NPM。这是因为Appium是用JavaScript编写的，需要Node.js作为运行环境来执行。您可以从Node.js的官方网站上下载和安装。在安装完成后，您可以通过在终端中键入“node -v”和“npm -v”两个命令来验证节点和NPM的安装是否成功。
2. 安装Appium
在安装完Node.js和NPM之后，您可以使用以下命令安装Appium：
“`bash
npm install -g appium
“`
这个命令将自动从NPM库中下载和安装Appium。您可以在终端中使用“appium -v”命令来检查Appium的版本是否正确安装。
3.启动Appium服务器
启动Appium服务器的方法有两种，分别是通过命令行和Appium桌面应用程序。
通过命令行启动Appium服务器
您可以通过以下命令在终端中启动Appium服务器：
“`bash
appium
“`
这将在默认端口4723上启动Appium服务器。如果要使用不同的端口号，请使用以下命令：
“`bash
appium -p
“`
通过Appium桌面应用程序启动Appium服务器
Appium桌面应用程序是一种简单易用的跨平台工具，可以帮助您管理移动应用自动化测试流程。如果您更喜欢使用GUI，可以下载和安装Appium桌面应用程序，然后按照以下步骤启动Appium服务器：
1. 打开Appium桌面应用程序。
2. 单击“Start Server”按钮。
3. 等待Appium服务器启动。
无论您使用哪种方法启动Appium服务器，都会在终端或Appium桌面应用程序中看到类似于以下信息的输出：
“`bash
[Appium] Welcome to Appium v1.20.2
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
“`
以上信息指示Appium服务器已经成功启动，并且在默认端口4723上监听REST请求。
结束语
相关问题拓展阅读：
Appium超时错误连接到驱动程序时问题，怎么解决
问题
1. error: Failed to start an Appium session, err was: Error: Requested a new session but one was in progress
之前的会话没有关闭，然后你又运行了测试实例，也没有设置覆盖.
解决:
1. 重新停止appium服务，开启Appium服务
2. 在Genarel Setting那里设置覆盖Session，重启Appium
测试结束在AfterClass加driver.quit()
2. error: Failed to start an Appium session, err was: Error: Command failed: C:\Windows\system32\cmd.exe /s /c “D:\android-sdk-windows\platform-tools\adb.exe -s adb server version (32) doesn’t match this client (36); killing…
wait-for-device”
error: could not install artsocket listener: cannot bind to 127.0.0.1:5037:
没有链接上手机或者
模拟器
，请确认已经连接成功，重新链接
3. error: Android devices must be of API level 17 or higher. Please change your device to Selendroid or upgrade Android on your device.
手机系统低于4.2，appium不支持4.2.2以下的系统，请换一个手机或者模拟器来测试。
4. Error: Permission to start activity denied.
**activity在清单文件里面没添加Android:exported=”true”的话，你不能直接打开对应的activity，需要从启动页activity打开。
exported属性就是设置是镇野大否允许activity被其它程序调用**
5. error: Failed to start an Appium session, err was: Error: Activity used to start app doesn’t exist or cannot ve launched! Make usre it exists and is launchable activity
要打开的activity不存在，activity路径错误，改为完整正确的activity路径
6. error: Failed to start an Appium session, err was: Error: ‘java – version’ failed. Error: Command failed: C:\Windows\system32\cmd.exe /s /c “java -version”
Java版本错误，请安装最新的版本。
7.> info: Error: Command failed: C:\Windows\system32\cmd.exe /s /c “D:\android-sdk-windows\platform-tools\adb.exe -s 8806a0b0 shell “echo ‘ready'”error: unknown host service
链接脊烂手机失败，重新链接手机即可，我就是重新拔插了一下u
Error: Command failed: C:\Windows\system32\cmd.exe /s /c “D:\android-sdk-windows\platform-tools\adb.exe -s 8806a0b0 shell “echo ‘ping'””
error: unknown host service
adb被突然占用导致，例如你在运行
用例
的时候运行了模拟器。
8. UIAutomatorViewer提示: Unable to connect to adb. Check if adb is installed correctly
解决，sdk升级御竖到了25产生的问题。
解决方法:
将adb.exe 复制一份到uiautomatorviewer
.bat
目录下
修改uiautomatorviewer.
bat文件
最后一行（改binddir=%prog_dir%为自己的platform-tools本地路径）
9 error: Failed to start an Appium session, err was:INSTALL_FAILED_ALREADY_EXISTS: Attempt to re-install io.appium.settings without first uninstalling
When you are at final step to execute test automation script for mobile app testing on a mobile emulator or a virtual device or a real device, you might observe that script execution fails with different kinds of errors, In context to current article you will look at the error and solutions for: INSTALL_FAILED_ALREADY_EXISTS: Attempt to re-install io.appium.settings without first uninstalling.
Error in Appium Server:
Error: Command failed: C:\Windows\system32\cmd.exe /s /c
“C:\Users\{User}\AppData\Local\Android\sdk\platform-tools\adb.exe -s
emulator-5554 install
“C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk””
> Failed to install C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\
settings_apk-debug.apk: Failure
io.appium.settings without first uninstalling.>
Error in Android studio run console:
org.openqa.selenium.SessionNotCreatedException: A new session could not be created.
(Original error: Command failed: C:\Windows\system32\cmd.exe /s /c
“C:\Users\{User}\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 install
“C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk””
Failed to install C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\
settings_apk-debug.apk: Failure
io.appium.settings without first uninstalling.>
) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
For the first time when you execute the script it might pass, but it will fail with above error when you try to execute the same or any other script multiple times. Or when your test script execution fails on the first attempt for some other reason, and when you fix it and execute it again, you might encounter this new issue.
原因：
The reason for this error is that Appium installs 2 mobile applications before executing the script.
1. io.appium.settings
2. io.appium.unlock
These are the supportive mobile applications appium utilizes to execute the test automation script in Mobile Emulator or virtual device or a real mobile device.
Ideally Appium should remove these files every time at the end of the script execution or termination, if it is intends to install them every time a script is executed, or it should conditionally install these apps / apks to the mobile emulator or mobile device.
In your mobile emulator / Virtual Device / Real device, the 2 mobile applications appear as below:
There are multiple ways to troubleshoot this error and go ahead for a successful test script execution.
解决办法
Solution 1: ADB’s uninstall command to remove the files.
You can open command prompt, assuming that you already had set the environment variables for ANDROID_HOME and Path variables for sdk tools and platform tools.
And execute commands as shown below:
Solution 2: Uninstall manually
You can open the mobile emulator / virtual device / real device and go to apps and uninstall them.
Solution 3: Write code as part of your test automation script.
As part of your selenium test automation script, you could write instructions to execute the commands provided in solution 1 above, so that this issue would not arise.
Hope this article has been helpful and you are able to proceed further with script execution.
Request to kindly share any of your queries in form of comments, we would try our best to provide any solution for you.
10. 出错信息里含有”ps ‘uiautomator’，具体信息未 A new session could not be created. (Original error: Command failed: C:\Windows\system32\cmd.exe /s /c “C:\Users\sxie\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell “ps ‘uiautomator'””
android-appium: A new session could not be created
junitexceptionandroidappium自动化
detail log:
org.openqa.selenium.SessionNotCreatedException: A new session could not be created. (Original error: Command failed: C:\Windows\system32\cmd.exe /s /c “C:\Users\sxie\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell “ps ‘uiautomator'””
) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
Build info: version: ‘3.4.0’, revision: ‘unknown’, time: ‘unknown’
System info: host: ‘WL’, ip: ‘10.110.12.39’, os.name: ‘Windows 8.1’, os.arch: ‘x86’, os.version: ‘6.3’, java.version: ‘1.8.0_40’
Driver info: driver.version: AndroidDriver
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:215)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:167)
at io.appium.java_client.remote.AppiumProtocolHandShake.createSession(AppiumProtocolHandShake.java:161)
at io.appium.java_client.remote.AppiumProtocolHandShake.createSession(AppiumProtocolHandShake.java:76)
at io.appium.java_client.remote.AppiumCommandExecutor.doExecute(AppiumCommandExecutor.java:111)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:162)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:637)
at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:42)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:1)
at io.appium.java_client.android.AndroidDriver.execute(AndroidDriver.java:1)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:250)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:236)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:137)
at io.appium.java_client.DefaultGenericMobileDriver.(DefaultGenericMobileDriver.java:38)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:88)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:112)
at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:73)
at com.sky.demo.ContactTest.setUp(ContactTest.java:44)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
==========================================
直接在cmd中执行”C:\Windows\system32\cmd.exe /s /c “C:\Users\sxie\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell “ps ‘uiautomator'””
bad pid ‘uiautomator'”， 报错： bad pid ‘uiautomator’
代码内容为
public class ContactTest {
private AndroidDriver driver;
@Before
public void setUp() throws Exception {
//设置apk的路径
File classpathRoot = new File(System.getProperty(“user.dir”));
File appDir = new File(classpathRoot, “apps”);
File app = new File(appDir, “ContactManager.apk”);
//设置自动化相关参数
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability(CapabilityType.BROWSER_NAME, “”);
capabilities.setCapability(“automationName”,”Appium”);
capabilities.setCapability(“platformName”, “Android”);
capabilities.setCapability(“deviceName”, “Pixel_XL_API_25”);// Galaxy_Nexus_API_25
capabilities.setCapability(“noReset”, true);
capabilities.setCapability(“avdReadyTimeout”,);
capabilities.setCapability(“sessionOverride”, true);
//设置安卓系统版本
capabilities.setCapability(“platformVersion”, “7.1.1”);
//设置apk路径
capabilities.setCapability(“app”, app.getAbsolutePath());
//设置app的主包名和主类名
capabilities.setCapability(“appPackage”, “com.example.android.contactmanager”);
capabilities.setCapability(“appActivity”, “.ContactManager”);
//初始化
driver = new AndroidDriver(new URL(” capabilities);
driver.manage().timeouts().implicitlyWait(10,TimeUnit.SECONDS);
}
@Test
public void addContact(){
WebElement el = driver.findElement(By.name(“Add Contact”));
el.click();
List textFieldsList = driver.findElementsByClassName(“android.widget.EditText”);
textFieldsList.get(0).sendKeys(“feimaoyuzhubaobao”);
textFieldsList.get(2).sendKeys(“forever together”);
driver.swipe(100, 500, 100, 100, 2);
driver.findElementByName(“Save”).click();
}
@After
public void tearDown() throws Exception {
driver.quit();
}
}
解决办法：
resolved by this way:
adb.js(C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js) 中1035 行this.shell(“ps ‘” + name + “‘”, function (err, stdout) {
对应执行的指令是ps ‘uiautomator’, Android7不支持这个指令格式，所以执行结果是bad pid ‘uiautomator’
目前Appium未对此进行处理,所以需要修改此指令的执行方式
即将
this.shell(“ps ‘” + name + “‘”, function (err, stdout) {
if (err) return cb(err);
替换成
this.shell_grep(“ps”, name, function (err, stdout) {
if (err) {
logger.debug(“No matching processes found”);
return cb(null, );
}
并增加上面用到的shell_grep函数：
ADB.prototype.shell_grep = function (cmd, grep, cb) {
if (cmd.indexOf(‘”‘) === -1) {
cmd = ‘”‘ + cmd + ‘”‘;
}
var execCmd = ‘shell ‘ + cmd + ‘| grep ‘ + grep;
this.exec(execCmd, cb);
};
11.Android 7.0系统的手机无法执行appium脚本的问题
Appium Appium 版本 1.4.16，Android 设备固件 7.x，执行脚本时，报错使用语言：python报错如下：
WebDriverException: Message: A new session could not be created. (Original error: Could not extract PIDs from ps output. PIDS: , Procs: )
这个是因为appium版本1.4.16 使用的 uiatumator1.0不支持的原因导致？如果不升级appium版本，是否有解决方案？
解决办法
uiautomator1.0应该是不支持7.0，不升版本就换用uiautomator2.0吧，或者用下面的改脚本的方法使用。
解决Android 7.0系统的手机无法执行appium脚本的问题，改问题的具体解决方法如下：
找到appium的安装目录下的adb.js文件，windows版本的目录如下：Appium\node_modules\appium\node_modules\appium-adb\lib
2、 打开adb.js，手动修改该文件下的内容，此方法我已经试验成功。
adb.js 中1035 行this.shell(“ps ‘” + name + “‘”, function (err, stdout) {
对应执行的指令是ps ‘uiautomator’, Android7不支持这个指令格式，所以执行结果是bad pid ‘uiautomator’
目前Appium未对此进行处理,所以需要修改此指令的执行方式
即将
this.shell(“ps ‘” + name + “‘”, function (err, stdout) {
if (err) return cb(err);
替换成
this.shell_grep(“ps”, name, function (err, stdout) {
if (err) {
logger.debug(“No matching processes found”);
return cb(null, );
}
并增加上面用到的shell_grep函数：
ADB.prototype.shell_grep = function (cmd, grep, cb) {
if (cmd.indexOf(‘”‘) === -1) {
cmd = ‘”‘ + cmd + ‘”‘;
}
var execCmd = ‘shell ‘ + cmd + ‘| grep ‘ + grep;
this.exec(execCmd, cb);
};
网上还有如下的修改解决办法：以下我未试验。
ADB.prototype.getPIDsByName = function (name, cb) {
logger.debug(“Getting all processes with ‘” + name + “‘”);
this.shell(“ps ‘” + name + “‘”, function (err, stdout) {
if (err) return cb(err);
stdout = stdout.trim();
var procs = ;
var outlines = stdout.split(“\n”);
outlines.shift(); //在该处添加此行代码
3、重启appium
技巧
1. 每次测试都重新安装app
为capabilities色设置noReset为true
capabilities.setCapability(“noReset”, true);
2. 中文乱码
这都是编码问题:
1.方法1:
Android Studio修改文件编码的方法，更底部的UTf-8,点击选GBK就可以了，reload文件。（ps: 先把文件内容全选复制一下再转换编码，再粘贴，不然文件内容就变乱码了）
2.方法2:
用的是原来的UTF-8编码，然后在测试module的build.gradle里面添加三行代码
tasks.withType(JavaCompile){
options.encoding = ‘UTF-8’
}
3. 清除编辑框EditText内容
这个问题好像是看手机系统的，我之前的手机就会出现sendKeys的时候没有全选去掉本来的内容，现在都会自动全选覆盖了，这个也不算问题了。
/**
* 逐字删除编辑框中的文字
* @param element 文本框架控件
*/
public void clearText(AndroidElement element){
String className = element.getClass().getSimpleName();
if (className.equals(“EditText”)){
String text = element.getText();
//跳到最后
driver.pressKeyCode(KEYCODE_MOVE_END);
for (int i = 0; i adb shell ime list -s
com.baidu.input_mi/.ImeService
com.sohu.inputmethod.sogou.xiaomi/.SogouIME
io.appium.android.ime/.UnicodeIME
C:\Users\LITP>
执行adb命令
先写好一个执行cmd的方法
/**
* 执行adb命令
* @param s 要执行的命令
*/
private void excuteAdbShell(String s) {
Runtime runtime=Runtime.getRuntime();
try{
runtime.exec(s);
}catch(Exception e){
print(“执行命令:”+s+”出错”);
}
}
在需要搜索的时候执行下面的代码，切换的输入法用自己查看列表的输入法内容，我这里是搜狗输入法
//使用adb shell 切换输入法-更改为搜狗拼音，这个看你本来用的什么输入法
excuteAdbShell(“adb shell ime set com.sohu.inputmethod.sogou.xiaomi/.SogouIME”);
//再次点击输入框，调取键盘，软键盘被成功调出
clickView(page.getSearch());
//点击右下角的搜索，即ENTER键
pressKeyCode(AndroidKeyCode.ENTER);
//再次切回 输入法键盘为Appium unicodeKeyboard
appium怎么开启服务器的介绍就聊到这里吧，感谢你花时间阅读本站内容，更多关于appium怎么开启服务器,Appium服务器如何开启？,Appium超时错误连接到驱动程序时问题，怎么解决的信息别忘了在本站进行查找喔。
