Appium输入慢的原因分析

冬瓜 — Sat, 27 May 2017 09:35:00 GMT

使用appium输入中文�Q�发现好慢！臛_��5�U�以上，如果在这��L��情况下做��试�Q�这��好悲剧了�?nbsp;

从appium�Q?.6.3)代码上来看，没有什么问题，直接是通过boostrap的setText的方法。说是就下蝲了appium-bootstrap的代码看�Q�从�q�里开发找到的代码�Q�都是java的代码，扑ֈ� io.appium.android.bootstrap.handler.SetText

在new Clear().execute(command);旉��长达5�U�（打日志发玎ͼ��Q�不��文本框有没有内容，都会执行

然后�Q�我们再看Clear的代�?/div>

/*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* See the NOTICE file distributed with this work for additional
* information regarding copyright ownership.
* You may obtain a copy of the License at
*
*     http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/

package io.appium.android.bootstrap.handler;

import android.graphics.Rect;
import android.os.SystemClock;
import android.view.InputDevice;
import android.view.KeyCharacterMap;
import android.view.KeyEvent;
import com.android.uiautomator.core.UiObject;
import com.android.uiautomator.core.UiObjectNotFoundException;
import com.android.uiautomator.core.UiSelector;
import io.appium.android.bootstrap.AndroidCommand;
import io.appium.android.bootstrap.AndroidCommandResult;
import io.appium.android.bootstrap.AndroidElement;
import io.appium.android.bootstrap.CommandHandler;
import io.appium.android.bootstrap.Logger;
import io.appium.android.bootstrap.WDStatus;
import io.appium.uiautomator.core.InteractionController;
import io.appium.uiautomator.core.UiAutomatorBridge;
import org.json.JSONException;

import java.lang.reflect.InvocationTargetException;

/**
* This handler is used to clear elements in the Android UI.
*
* Based on the element Id, clear that element.
*
* UiAutomator method clearText is flaky hence overriding it with custom implementation.
*/
public class Clear extends CommandHandler {

  /*
   * Trying to select entire text with correctLongClick and increasing time intervals.
   * Checking if element still has text in them and and if true falling back on UiAutomator clearText
   *
   * @param command The {@link AndroidCommand}
   *
   * @return {@link AndroidCommandResult}
   *
   * @throws JSONException
   *
   * @see io.appium.android.bootstrap.CommandHandler#execute(io.appium.android.
   * bootstrap.AndroidCommand)
   */
  @Override
  public AndroidCommandResult execute(final AndroidCommand command)
          throws JSONException {
    if (command.isElementCommand()) {
      try {
        final AndroidElement el = command.getElement();

        // first, try to do native clearing
        Logger.debug("Attempting to clear using UiObject.clearText().");
        el.clearText();  //无条仉��会执行这块。然后再分析clearText
        if (el.getText().isEmpty()) {
          return getSuccessResult(true);
        }

        // see if there is hint text
        if (hasHintText(el)) {
          Logger.debug("Text remains after clearing, "
              + "but it appears to be hint text.");
          return getSuccessResult(true);
        }

        // next try to select everything and delete
        Logger.debug("Clearing text not successful. Attempting to clear " +
                "by selecting all and deleting.");
        if (selectAndDelete(el)) {
          return getSuccessResult(true);
        }

        // see if there is hint text
        if (hasHintText(el)) {
          Logger.debug("Text remains after clearing, "
              + "but it appears to be hint text.");
          return getSuccessResult(true);
        }

        // finally try to send delete keys
        Logger.debug("Clearing text not successful. Attempting to clear " +
                "by sending delete keys.");
        if (sendDeleteKeys(el)) {
          return getSuccessResult(true);
        }

        if (!el.getText().isEmpty()) {
          // either there was a failure, or there is hint text
          if (hasHintText(el)) {
            Logger.debug("Text remains after clearing, " +
                    "but it appears to be hint text.");
            return getSuccessResult(true);
          } else if (!el.getText().isEmpty()) {
            Logger.debug("Exhausted all means to clear text but '" +
                    el.getText() + "' remains.");
            return getErrorResult("Clear text not successful.");
          }
        }
        return getSuccessResult(true);
      } catch (final UiObjectNotFoundException e) {
        return new AndroidCommandResult(WDStatus.NO_SUCH_ELEMENT,
            e.getMessage());
      } catch (final Exception e) { // handle NullPointerException
        return getErrorResult("Unknown error clearing text");
      }
    }
    return getErrorResult("Unknown error");
  }

  private boolean selectAndDelete(AndroidElement el)
      throws UiObjectNotFoundException, IllegalAccessException,
        InvocationTargetException, NoSuchMethodException {
    Rect rect = el.getVisibleBounds();
    // Trying to select entire text.
    TouchLongClick.correctLongClick(rect.left + 20, rect.centerY(), 2000);
    UiObject selectAll = new UiObject(new UiSelector().descriptionContains("Select all"));
    if (selectAll.waitForExists(2000)) {
      selectAll.click();
    }
    // wait for the selection
    SystemClock.sleep(500);
    // delete it
    UiAutomatorBridge.getInstance().getInteractionController().sendKey(KeyEvent.KEYCODE_DEL, 0);

    return el.getText().isEmpty();
  }

  private boolean sendDeleteKeys(AndroidElement el)
      throws UiObjectNotFoundException, IllegalAccessException,
        InvocationTargetException, NoSuchMethodException {
    String tempTextHolder = "";

    // Preventing infinite while loop.
    while (!el.getText().isEmpty() && !tempTextHolder.equalsIgnoreCase(el.getText())) {
      // Trying send delete keys after clicking in text box.
      el.click();
      // Sending delete keys asynchronously, both forward and backward
      for (int key : new int[] { KeyEvent.KEYCODE_DEL, KeyEvent.KEYCODE_FORWARD_DEL }) {
        tempTextHolder = el.getText();
        final int length = tempTextHolder.length();
        final long eventTime = SystemClock.uptimeMillis();
        KeyEvent deleteEvent = new KeyEvent(eventTime, eventTime, KeyEvent.ACTION_DOWN,
                key, 0, 0, KeyCharacterMap.VIRTUAL_KEYBOARD, 0, 0,
                InputDevice.SOURCE_KEYBOARD);
        for (int count = 0; count < length; count++) {
          UiAutomatorBridge.getInstance().injectInputEvent(deleteEvent, false);
        }
      }
    }

    return el.getText().isEmpty();
  }

  private boolean hasHintText(AndroidElement el)
      throws UiObjectNotFoundException, IllegalAccessException,
        InvocationTargetException, NoSuchMethodException {
    // to test if the remaining text is hint text, try sending a single
    // delete key and testing if there is any change.
    // ignore the off-chance that the delete silently fails and we get a false
    // positive.
    String currText = el.getText();

    try {
      if (!el.getBoolAttribute("focused")) {
        Logger.debug("Could not check for hint text because the element is not focused!");
        return false;
      }
    } catch (final Exception e) {
      Logger.debug("Could not check for hint text: " + e.getMessage());
      return false;
    }

    InteractionController interactionController = UiAutomatorBridge.getInstance().getInteractionController();
    interactionController.sendKey(KeyEvent.KEYCODE_DEL, 0);
    interactionController.sendKey(KeyEvent.KEYCODE_FORWARD_DEL, 0);

    return currText.equals(el.getText());
  }
}

再看看AndroidElement.clearText是什么样�?/div>

  public void clearText() throws UiObjectNotFoundException {
    el.clearTextField();
  }

�q�个都就是com.android.uiautomator.core.UiObject.clearTextField

于是扑ֆ�扑ֈ�uiautomator的代码再来分析（�q�个代码需要下载andriod sdk,在对应android版本的目录下�Q�会有源码，也有uiautomator的源代码),我这里的路径是：

Android\sdk\sources\android-19\com\android\uiautomator\core

在UiObject.java扑ֈ�clearTextField实现

/**
     * Clears the existing text contents in an editable field.
     *
     * The {@link UiSelector} of this object must reference a UI element that is editable.
     *
     * When you call this method, the method first sets focus at the start edge of the field.
     * The method then simulates a long-press to select the existing text, and deletes the
     * selected text.
     *
     * If a "Select-All" option is displayed, the method will automatically attempt to use it
     * to ensure full text selection.
     *
     * Note that it is possible that not all the text in the field is selected; for example,
     * if the text contains separators such as spaces, slashes, at symbol etc.
     * Also, not all editable fields support the long-press functionality.
     *
     * @throws UiObjectNotFoundException
     * @since API Level 16
     */
    public void clearTextField() throws UiObjectNotFoundException {
        Tracer.trace();
        // long click left + center
        AccessibilityNodeInfo node = findAccessibilityNodeInfo(mConfig.getWaitForSelectorTimeout());
        if(node == null) {
            throw new UiObjectNotFoundException(getSelector().toString());
        }
        Rect rect = getVisibleBounds(node);
        getInteractionController().longTapNoSync(rect.left + 20, rect.centerY()); //长按
        // check if the edit menu is open
        UiObject selectAll = new UiObject(new UiSelector().descriptionContains("Select all"));
        if(selectAll.waitForExists(50))
            selectAll.click();
        // wait for the selection
        SystemClock.sleep(250); //�q�里�{?50ms
        // delete it
        getInteractionController().sendKey(KeyEvent.KEYCODE_DEL, 0);
    }

�怿�大家�Q�可以找到慢的原因了。这里做一�ơ长按，然再再做全选，然后再sleep(250)�Q�还有一个selectAll.waitForExists(50)�Q?�q�些都是耗费旉��的�?/div>

再找一下UiObject.java中setText的实�?/div>

    public boolean setText(String text) throws UiObjectNotFoundException {
        Tracer.trace(text);
        clearTextField();
        return getInteractionController().sendText(text);
    }

发现�q�里又调用了一�ơclearTextField�Q�这��L��来，设一�ơ文本，都会清理两次文本�Q�于是，�q�时间就长了�?nbsp;

优化�Q�只需要将io.appium.android.bootstrap.handler.SetText中的new Clear().execute(command)��L��可以了�?/div>

冬瓜 2017-05-27 17:35 发表评论

appium的一个内存泄露bug

冬瓜 — Thu, 23 Feb 2017 12:35:00 GMT

摘要: �?关于node-heapdump��L�� 使用node heapdump

��Z��appium源码 1.6.3 �q�行,发现�q�行一�D�|��间后,会出现内存溢�?
用node-heapdump生成heap快照发现多了很多字符串对�?内容如下阅读全文

冬瓜 2017-02-23 20:35 发表评论

使用node heapdump

冬瓜 — Thu, 23 Feb 2017 06:28:00 GMT

摘要: 在��用appium的过�E�中�Q�发现有内存泄露�Q�最后就process out of memory了，��挂�?
�|�上用��用增加运行内存的方式(�q�是抗不�?�Q�没办法�Q�就只好扑և�内存泄露的地方了
对node.js很多文章�Q�都是说用memwatch�Q�结果发玎ͼ��q�个是一个死��目�Q�有四年没有更新�q�了�Q�在现有的环境下�Q�是没有办法�~�译的�?
然后又有一个memwatch-next�Q�顾名思义�Q�就是memwatch的下一个版本，�l�果是果然也可以�~�译�Q�一些事件也支持�Q�但是要headdump后要end后，��挂了�?
国内�Q�用癑ֺ��Q�你一万年都别惌��决问题，估计找成��Z��宜的东西�Q�百度世界第一名，google也不比过癑ֺ��?nbsp; 阅读全文

冬瓜 2017-02-23 14:28 发表评论

appium的source�q�回的xml字符串处理的工具函数

冬瓜 — Mon, 20 Feb 2017 06:31:00 GMT

摘要: �q�里是基于node的xmldom上扩展的工具�Q�在使用appium的时候，常常需要用source功能来分析当前上下文�Q�所以扩展了若干函数�Q�用于分析。这些代码是��Z��node 6.9.x JavaScript ES6语法实现。（关于如何在node使用ES6的语法，请参考我的前文：js�W�记�?node 6.9.x for gulp完整配置�q�程�Q�完成代码如下：xml_utils.jsCo... 阅读全文

冬瓜 2017-02-20 14:31 发表评论

appium的UiAutomator exited unexpectedly(1.6.3)

冬瓜 — Wed, 08 Feb 2017 06:39:00 GMT

今天用新手机�Q�运行appium 1.6.3 ��试�Q�发现日志打印如下错误：

[debug] [ADB] Creating ADB subprocess with args: ["-P",5037,"-s","xxxxxxxxxxx","shell","uiautomator","runtest","AppiumBootstrap.jar","-c","io.appium.android.bootstrap.Bootstrap","-e","pkg","com.tencent.mm","-e","disableAndroidWatchers",false,"-e","acceptSslCerts",false]

[UiAutomator] UiAutomator exited unexpectedly with code 0, signal null
仔细看日志发�?/span>�Q�发�?data/local/tmp�~�少AppiumBootstrap.jar

然后在appium的node_module目录下面�?/span>appium-android-bootstrap\bootstrap\bin扑ֈ�AppiumBootstrap.jar�Q�然后复制到/data/local/tmp���可以，然后再运行，���试OK

冬瓜 2017-02-08 14:39 发表评论

冬瓜 — Fri, 06 Jan 2017 09:45:00 GMT

摘要: 从appium 1.3.3�?��支持unicode输入,也就是可以输入中文了.
实际�q�行环境�Q?nbsp; 阅读全文

冬瓜 2017-01-06 17:45 发表评论

为appium配置gulp es2017 to node 6.9.x

冬瓜 — Thu, 22 Dec 2016 03:15:00 GMT

摘要: 默认情况�?appium是��用appium-gulp-plugins��代码�{由es2015+转换为es5
它用上了es2017的特�?await和async
但是用它调用gulp watch的时�?常常报错.....
现在node.js已经到达�?.9.x,已经99%支持es2015(es6),所以这里重调新调一�?nbsp; 阅读全文

冬瓜 2016-12-22 11:15 发表评论

安装appium-selendroid-driver

冬瓜 — Tue, 20 Dec 2016 09:34:00 GMT

摘要: 阅读全文

冬瓜 2016-12-20 17:34 发表评论