An element could not be located on the page using the given search parameters.

最新推荐文章于 2022-09-06 15:46:45 发布
最新推荐文章于 2022-09-06 15:46:45 发布
阅读量6.5k 收藏 1
点赞数 1
文章标签： selenium appium API 自动化测试
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_44605463/article/details/107143786
版权

Appium中【MJSONWP】错误

Appium自动化测试错误提示An element could not be located on the page using the given search parameters

最近在学习自动化测试由Python语言转向Java语言，前者测试同一APP可流畅运行，后者可启动APP，但一到相关定位时就没反应，Appium日志显示错误信息，Eclipse控制台报错，不知道是哪里出了问题希望得当帮助，谢谢各位！

错误截图

Eclipse错误截图: EclipEclipse控制台错误se控制台错误
APP启动界面截图：
默认启动APP页面
Appium日志截图：
Appium错误提示
项目结构截图：
在这里插入图片描述
测试代码截图：
在这里插入图片描述
在这里插入图片描述

代码

测试代码：

package qichezhijia;

import static org.junit.Assert.assertEquals;

import java.net.URL;
import java.util.concurrent.TimeUnit;

import org.junit.After;
import org.junit.Before;
import org.junit.Test;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.openqa.selenium.support.ui.WebDriverWait;

import io.appium.java_client.android.AndroidDriver;
import io.appium.java_client.android.AndroidKeyCode;

public class QIche {
	 private AndroidDriver  driver;
	    private WebDriverWait wait;
	  
	   @Before
	  public void setup() throws Exception {
	        DesiredCapabilities cap = new DesiredCapabilities();
	        cap.setCapability("browserName", "");   //这里不需要设置浏览器,只有H5模式才设置为"chrome"或系统原始浏览器"browser" 
	        cap.setCapability("platformName", "Android"); //指定测试平台
	        //雷电安卓模拟器
	        cap.setCapability("deviceName", "emulator-5554"); //指定测试机的ID,通过adb命令`adb devices`获取
	        cap.setCapability("platformVersion", "5.1"); 
	        //安卓真机
	        //cap.setCapability("deviceName", "68U5T17A08002290"); //指定测试机的ID,通过adb命令`adb devices`获取
	        //cap.setCapability("platformVersion", "7.0"); 
	        
	        //将上面获取到的包名和Activity名设置为值
	        cap.setCapability("appPackage", "com.cubic.autohome");
	        cap.setCapability("appActivity", "com.cubic.autohome.LogoActivity");
	        
	        //A new session could not be created的解决方法
	        cap.setCapability("appWaitActivity","com.cubic.autohome.LogoActivity");
	        //每次启动时覆盖session，否则第二次后运行会报错不能新建session
	        cap.setCapability("sessionOverride", "true");
	        
	        //设置app每次运行不被重新初始化
	        cap.setCapability("noReset","true");
	        cap.setCapability("fullReset","false"); 
	        
	        //设置使用unicode键盘，支持输入中文和特殊字符
	        cap.setCapability("unicodeKeyboard", "true");
	        //设置用例执行完成后重置键盘
	        cap.setCapability("resetKeyboard", "true");
	        cap.setCapability("noSign", "true");
	        
	        //使用UiAutomator2框架便于获取toast信息
	        cap.setCapability("automationName", "UiAutomator2");
	        
	        driver = new AndroidDriver(new URL("http://127.0.0.1:4723/wd/hub"), cap);
	        wait = new WebDriverWait(driver, 15); 
	        driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);//隐式等待,最大超时10秒
	  }
	   
	  @Test
	  public void TestBig() throws InterruptedException{
		
		  driver.findElementByXPath("//android.widget.TextView[@text='下次再说']").click();
		  driver.findElementById("com.autohome.main.article:id/iv_search").click();
		  Thread.sleep(1000);
		  driver.findElementById("com.autohome.plugin.search:id/fragment_search_keyword_autocompleteview").sendKeys("大黄蜂");
	  
	      
	  }
	  
	   
	  @After
	  public void tearDown() throws Exception {
		  Thread.sleep(1000);   //暂停1秒
		  driver.quit();//关闭
	  }

}

控制台错误代码：

org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: Cannot start the 'com.cubic.autohome' application. Original error: 'com.cubic.autohome.LogoActivity' or 'com.cubic.autohome.com.cubic.autohome.LogoActivity' never started (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 61.17 seconds
Build info: version: '3.6.0', revision: '6fbf3ec777', time: '2017-09-27T16:15:26.402Z'
System info: host: 'KIPKANG', ip: '192.168.100.1', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_251'
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:214)
	at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
	at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$new$0(JsonWireProtocolResponse.java:53)
	at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$getResponseFunction$2(JsonWireProtocolResponse.java:91)
	at org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$24(ProtocolHandshake.java:359)
	at java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
	at java.util.Spliterators$ArraySpliterator.tryAdvance(Unknown Source)
	at java.util.stream.ReferencePipeline.forEachWithCancel(Unknown Source)
	at java.util.stream.AbstractPipeline.copyIntoWithCancel(Unknown Source)
	at java.util.stream.AbstractPipeline.copyInto(Unknown Source)
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
	at java.util.stream.FindOps$FindOp.evaluateSequential(Unknown Source)
	at java.util.stream.AbstractPipeline.evaluate(Unknown Source)
	at java.util.stream.ReferencePipeline.findFirst(Unknown Source)
	at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:362)
	at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:136)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:142)
	at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:89)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	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:217)
	at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:140)
	at io.appium.java_client.DefaultGenericMobileDriver.<init>(DefaultGenericMobileDriver.java:38)
	at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:83)
	at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:93)
	at io.appium.java_client.android.AndroidDriver.<init>(AndroidDriver.java:72)
	at qichezhijia.QIche.setup(QIche.java:55)
	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:86)
	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:538)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:760)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:460)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:206)

java.lang.NullPointerException
	at qichezhijia.QIche.tearDown(QIche.java:80)
	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.RunAfters.evaluate(RunAfters.java:33)
	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:86)
	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:538)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:760)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:460)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:206)

Appium日志代码：

Logcat] Stopping logcat capture
[ADB] Removing forwarded port socket connection: 8204 
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward --remove tcp\:8204'
[BaseDriver] Event 'newSessionStarted' logged at 1593943854948 (18:10:54 GMT+0800 (中国标准时间))
[MJSONWP] Encountered internal error running command: Error: Cannot start the 'com.cubic.autohome' application. Original error: 'com.cubic.autohome.LogoActivity' or 'com.cubic.autohome.com.cubic.autohome.LogoActivity' never started
[MJSONWP]     at ADB.callee$0$0$ (C:\Users\清濑灰二\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\lib\tools\apk-utils.js:125:11)
[MJSONWP]     at tryCatch (C:\Users\清濑灰二\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:67:40)
[MJSONWP]     at GeneratorFunctionPrototype.invoke [as _invoke] (C:\Users\清濑灰二\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:315:22)
[MJSONWP]     at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (C:\Users\清濑灰二\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:100:21)
[MJSONWP]     at GeneratorFunctionPrototype.invoke (C:\Users\清濑灰二\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:136:37)
[MJSONWP]     at 
[HTTP] <-- POST /wd/hub/session 500 61106 ms - 307
[HTTP]

其他问题

使用的是老师给的APpiumDemo的java模板，在运行单机计算器时能正常运行，但换一下APP就出错了
-测试截图：
APP运行用例截图：
在这里插入图片描述
日志截图：
在这里插入图片描述
测试用例代码截图：
在这里插入图片描述
在这里插入图片描述

-照葫芦画瓢都能出错，实在是找不到哪里出了问题，孩子太难了，救救孩子吧。

真.菜鸡
关注
  • 1
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
appium_An element could not be located on the page using the given search parameters.
jss19940414的博客
05-05 1万+
问题描述: 使用find_element_by_xpath的时候报错，如下 Traceback (most recent call last): File "F:/project/appiumTest/weChart/moments.py", line 158, in <module> moments.smallexe() File "F:/project/ap...
Appinum: Message: An element could not be located on the page using the given search parameters.
热门推荐
紫色飞鱼儿的博客
03-30 1万+
运行报错： selenium.common.exceptions.NoSuchElementException: Message: An element could not be located on the page using the given search parameters. 就是页面跳转是需要时间的，但是代码执行是很快的，这里没有找到元素是因为，在获取id时，手机页面...
Appium学习笔记：Message: An element could not be located on the page using the given search parameters.
zoujing00的博客
01-26 4150
appium运行报错 错误原因：使用给定的搜索参数无法在页面上找到元素 app启动时有一个广告页面，这个页面跳转是需要时间的，但是代码执行是很快的，这里没有找到元素是因为，在获取id时，手机页面还没有进入到该页面，所以在页面上找不到元素 ...
Appium工作日记：Message: An element could not be located on the page using the given search parameters.
weixin_46404771的博客
07-30 574
程序运行2个月都没问题，突然报错，这突如其来的血压飙升` 报错代码如下： NoSuchElementException Traceback (most recent call last) <ipython-input-5-71fe1159ea05> in <module> 162 #需要更改，改为吉利车的出价时间 163 elif get_date('/hierarchy/android.widget.FrameL
解决selenium.common.exceptions.NoSuchElementException: Message: An element could not be located on...
Tacotl的博客
07-01 3518
场景：appium+python+selenium eg:driver.find_element_by_accessibility_id("搜索").click() 问题：selenium.common.exceptions.NoSuchElementException: Message: An element could not be located on the page using the given search parameters 解决：使用uiautomatorviewer.bat发现id全称
Python +appium 报错：NoSuchElementException: Message: An element could not be located on the page using
weixin_49018491的博客
06-30 1296
@TOCPython +appium 报错：NoSuchElementException: Message: An element could not be located on the page using the given search parameters. 找了好多的信息，都没有充分解决；最后解决方案：
TP.rar_131861com_C-C++_The Element_be6nc
09-23
The Meddle Element_In_List Insertion_Sort_Wth_C LinkedList selecton_Insertion_Sell_sort_Wth_C All_Sort
the-main-element-Gauss-.rar_The Element
07-15
在程序"the main element Gauss.txt"中，我们可以看到具体的实现逻辑。首先，它会读取输入的矩阵和向量数据，然后通过迭代过程执行列主元选取和行变换。在每次迭代中，程序会找到当前列的最大元素，将其所在行作为...
ib_recv.rar_The Element
09-24
标题 "ib_recv.rar_The Element" 提到的 "The Element" 在描述中被提及与一个列表操作有关，它被添加到了 "to list" 的尾部。这可能是指编程中的数据结构操作，尤其是链表操作。在计算机科学中，链表是一种线性数据...
ctx.rar_The Element
09-24
Set selected to false without notifying the owner media element. Used when another video track is selected, implicitly deselecting this one.
s30801.tsr.zip_TSR_The Element
07-14
标题 "s30801.tsr.zip_TSR_The Element" 暗示这是一个与技术相关的压缩包，其中可能包含一些数据文件或程序代码，而 "TSR" 可能是某种特定软件、系统或服务的缩写，可能是 "Technical Support Record" 或者 ...
selenium.common.exceptions.NoSuchElementException: Message: An element could not be located on the p
dlrb_beautiful的博客
11-16 1326
python+appium定位元素失败： 刚开始用的driver.find_element_by_id方法 报错信息如下： 解决办法： 1.使用driver.find_element_by_xpath方法 2.设置延时：time.sleep(5)导包：time.sleep(5)（因为页面还没有加载出来，代码就执行了搜索元素及点击事件，导致找不到元素） 采坑笔记：先是id进行定位，不成功；就改用class进行定位，还是不行；最后看了这位大佬的博文；设置延时真的很不错； https://blog.csdn.ne
Appium :只有一个NATIVE_APP，跳转页面后提示：NoSuchElementException: Message: An element could not be locate..
jianglianye21的博客
11-06 3478
这几天用appium写自动化，遇到一个问题，就是在A页面点击一个按钮进入B页面，B页面的元素怎么都获取不到。纠结了几天，在网上找了很多方法也没能解决，后来在官方文档看到： The UiAutomator2 Driver for Android Appium’s flagship support for automating Android apps is via the UiAutomator2 ...
python操作Appium的时候出现的错误selenium.common.exceptions.NoSuchElementException: Message: An element could n
qq_53582111的博客
10-20 3097
selenium.common.exceptions.NoSuchElementException: Message: An element could not be located on the page using the given search parameters. 错误原因是：1、不能被加载，需要等待的时间 2、我们的xpath写错了
find_element调用报错NoSuchElementError: An element could not be located on the page using the given sear
qq_45746739的博客
09-06 5414
出现的原因是第7行a.find_element(By.ID, 'im2510.hollcon.com.im2510:id/edit_account').send_keys("admin")中By.ID后面应该用双引号，用了单引号就报错了，改成双引号就能正常运行了，为什么用单引号这里报错还没有弄明白。
Appium常见错误
qq_39286483的博客
11-22 754
1.An element could not be located on the page using the given search parameters 没有找到该元素 原因:1.首先看是否是页面加载太慢,加一点延时.2.然后就是真的没有该元素
appium python在定位元素2个常见报错
mmhyy123的博客
03-24 903
被自己气死的第不知道几次 不看报错搞了几天这样 driver.find_element_by_id(‘com.dxda.supplychain3:id/checkbox’)[0].click() driver.find_elements_by_id(‘com.dxda.supplychain3:id/checkbox’)[0].click() 使用第一个函数是没有click方法 要用第二个函数 参...
啊噗嗯 demo调试记录
u014572426的专栏
07-29 567
问题1：一直NoSuchElementException: An element could not be located on the page 解决：在findelement之前加一句等待 driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);   问题2：中文输入是乱码 解决：加入了网上给的两句代码，并没有解决...
解决appium元素定位不到的问题
weixin_45305977的博客
07-26 1867
目录欢迎使用Markdown编辑器欢迎使用Markdown编辑器 欢迎使用Markdown编辑器 你好！ 这是你第一次使用 Markdown编辑器 所展示的欢迎页。如果你想学习如何使用Markdown编辑器, 可以仔细阅读这篇文章，了解一下Markdown的基本语法知识。@TOC 欢迎使用Markdown编辑器 你好！ 这是你第一次使用 Markdown编辑器 所展示的欢迎页。如果你想学习如何使用Markdown编辑器, 可以仔细阅读这篇文章，了解一下Markdown的基本语法知识。 ........
The given frequency argument could not be matched to the given index.
最新发布
05-14
This error message could be encountered in various scenarios based on the context of usage. In general, it indicates that the frequency value provided as an argument in the code does not correspond to any index value in the code or data structure being used. For example, if you are working with an array and trying to access an element at a particular frequency index that does not exist in the array, this error could be raised. Similarly, in signal processing or audio-related applications, this error could occur when trying to access a frequency bin that is out of range or does not exist. To fix this error, you should check the code carefully and ensure that the frequency value being used matches the index values expected by the code or data structure. You may need to adjust the frequency range or modify the code to handle out-of-range values gracefully.
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值