gpt4 book ai didi

android - Appium + Android + WebDriver findElement() : cannot find element after sendKeys()?

转载 作者:太空狗 更新时间:2023-10-29 15:53:39 25 4
gpt4 key购买 nike

我有一个模拟的 Android 设备和 Appium。我的测试成功地在特定文本字段中启动了正确的 Activity 和类型。但是当我试图找到相同的文本字段以检查其中的文本时,我得到 “使用给定的搜索参数无法在页面上找到元素。” 即使我尝试重新使用该元素而不是第二次搜索它,它仍然会失败并显示相同的消息。我应该怎么做?也许第二个 findElement() 的上下文是错误的——我也找不到文本字段旁边的按钮。

这是一个包含应用程序和测试项目的 git 存储库。失败的 JUnit 测试证明了这个问题:https://github.com/achengs/an-appium-question

下面的详细信息(代码和 Appium 日志交错)

这是第一个成功的 findElement。 Activity 的布局 xml 文件具有我正在寻找的文本字段的此属性:android:id="@+id/edit_message"

public static final String MESSAGE_TO_SEND = "edit_message";
...
WebElement e = driver.findElement(By.id(MESSAGE_TO_SEND));

首先findElement成功:

debug: Appium request initiated at /wd/hub/session/0ec259be-87e0-47f6-9279-da577fe29a07/element
debug: Request received with params: {"using":"id","value":"edit_message"}
info: Pushing command to appium work queue: ["find",{"strategy":"id","selector":"edit_message","context":"","multiple":false}]
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"find","params":{"strategy":"id","selector":"edit_message","context":"","multiple":false}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: find
info: [BOOTSTRAP] [debug] Finding edit_message using ID with the contextId:
info: [BOOTSTRAP] [info] Returning result: {"value":{"ELEMENT":"1"},"status":0}
info: Responding to client with success: {"status":0,"value":{"ELEMENT":"1"},"sessionId":"0ec259be-87e0-47f6-9279-da577fe29a07"}
POST /wd/hub/session/0ec259be-87e0-47f6-9279-da577fe29a07/element 200 5656ms - 109b

打个招呼!

String text = "hello!";
e.sendKeys(text);

成功了:

debug: Appium request initiated at /wd/hub/session/0ec259be-87e0-47f6-9279-da577fe29a07/element/1/value
debug: Request received with params: {"id":"1","value":["hello!"]}
info: Pushing command to appium work queue: ["element:setText",{"elementId":"1","text":"hello!"}]
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"element:setText","params":{"elementId":"1","text":"hello!"}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: setText
info: [BOOTSTRAP] [info] Returning result: {"value":true,"status":0}
info: Responding to client with success: {"status":0,"value":true,"sessionId":"0ec259be-87e0-47f6-9279-da577fe29a07"}
POST /wd/hub/session/0ec259be-87e0-47f6-9279-da577fe29a07/element/1/value 200 4215ms - 89b

这是失败的第二个 findElement。 (如果我跳过这个 findElement 并重新使用原来的那个——或者如果我试图找到文本字段旁边的发送按钮,我仍然会遇到类似的失败)

WebElement f = driver.findElement(By.id(MESSAGE_TO_SEND));

这是失败的日志:

debug: Appium request initiated at /wd/hub/session/0ec259be-87e0-47f6-9279-da577fe29a07/element
debug: Request received with params: {"using":"id","value":"edit_message"}
info: Pushing command to appium work queue: ["find",{"strategy":"id","selector":"edit_message","context":"","multiple":false}]
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"find","params":{"strategy":"id","selector":"edit_message","context":"","multiple":false}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: find
info: [BOOTSTRAP] [debug] Finding edit_message using ID with the contextId:
info: [BOOTSTRAP] [info] Returning result: {"value":"No element found","status":7}
info: Responding to client with error: {"status":7,"value":{"message":"An element could not be located on the page using the given search parameters.","origValue":"No element found"},"sessionId":"0ec259be-87e0-47f6-9279-da577fe29a07"}
POST /wd/hub/session/0ec259be-87e0-47f6-9279-da577fe29a07/element 500 874ms - 223b

存在对 HTML 的请求。我正在测试 native Android 应用程序。这是当前正在测试的 Activity 的布局 xml。如果我还应该在此处包含其他内容,请告诉我。

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:orientation="horizontal">
<EditText android:id="@+id/edit_message"
android:layout_weight="1"
android:layout_width="0dp"
android:layout_height="wrap_content"
android:hint="@string/edit_message" />
<Button
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="@string/button_send"
android:onClick="sendMessage" android:id="@+id/send"/>
</LinearLayout>

最佳答案

使用的 ID 不应是 "edit_message",而是 "com.company.app:id/edit_message"

基本上,如果您的 layout.xml 文件使用 android:id="@+id/foo" 为您的 UI 元素指定了一个 ID(并且您的应用程序是 com.company.app),那么在您的测试你应该使用 "com.company.app:id/foo" 而不仅仅是 "foo"

仅使用 "foo" 可能会找到 UI 元素,但与它进行一次交互后,您将无法在 UI 中找到任何内容。不知道这是为什么,但它混淆了事情。

关于android - Appium + Android + WebDriver findElement() : cannot find element after sendKeys()?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/20379744/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com