80943d8daa6ab31ab5c486d57aea406aa0730d58 |
|
02-Jan-2013 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding UI test automation APIs. This change adds APIs support for implementing UI tests. Such tests do not rely on internal application structure and can span across application boundaries. UI automation APIs are encapsulated in the UiAutomation object that is provided by an Instrumentation object. It is initialized by the system and can be used for both introspecting the screen and performing interactions simulating a user. UI test are normal instrumentation tests and are executed on the device. UiAutomation uses the accessibility APIs to introspect the screen and a special delegate object to perform privileged operations such as injecting input events. Since instrumentation tests are invoked by a shell command, the shell program launching the tests creates a delegate object and passes it as an argument to started instrumentation. This delegate allows the APK that runs the tests to access some privileged operations protected by a signature level permissions which are explicitly granted to the shell user. The UiAutomation object also supports running tests in the legacy way where the tests are run as a Java shell program. This enables existing UiAutomator tests to keep working while the new ones should be implemented using the new APIs. The UiAutomation object exposes lower level APIs which allow simulation of arbitrary user interactions and writing complete UI test cases. Clients, such as UiAutomator, are encouraged to implement higher- level APIs which minimize development effort and can be used as a helper library by the test developer. The benefit of this change is decoupling UiAutomator from the system since the former was calling hidden APIs which required that it is bundled in the system image. This prevented UiAutomator from being evolved separately from the system. Also UiAutomator was creating additional API surface in the system image. Another benefit of the new design is that now test cases have access to a context and can use public platform APIs in addition to the UiAutomator ones. Further, third-parties can develop their own higher level test APIs on top of the lower level ones exposes by UiAutomation. bug:8028258 Also this change adds the fully qualified resource name of the view's id in the emitted AccessibilityNodeInfo if a special flag is set while configuring the accessibility service. Also added is API for looking up node infos by this id. The id resource name is relatively more stable compared to the generaed id number which may change from one build to another. This API facilitate reuing the already defined ids for UI automation. bug:7678973 Change-Id: I589ad14790320dec8a33095953926c2a2dd0228b
/frameworks/base/test-runner/src/android/test/AndroidTestRunner.java
|
87571b75e6560d33b8de7ca04801612a20a04d98 |
|
03-Apr-2012 |
Brian Muramatsu <btmura@google.com> |
Try Alternate Constructor for Single Method Tests Some tests do not have a no argument constructor. If they don't have one, then try a constructor with a String argument. A lot of CTS tests from open source projects have different practices and may not have a no arg constructor. Change-Id: I87c490c22347a2f4b03c3125308be0d2259f9208
/frameworks/base/test-runner/src/android/test/AndroidTestRunner.java
|
e70f61b1160e953e5e4d18d30a463fa9ba821779 |
|
19-Feb-2010 |
Brett Chabot <brettchabot@android.com> |
Retry test-runner tests move. This time change the frameworks makefile so it only includes test-runner/src in the public API.
/frameworks/base/test-runner/src/android/test/AndroidTestRunner.java
|
c1ca8c51c616d1517b18bf24feaa9f8f1430c835 |
|
19-Feb-2010 |
Brett Chabot <brettchabot@android.com> |
Revert "Move framework test-runner unit tests to be closer to their source." This reverts commit 12093976a4842a795491cfd2b1d3b71e18503f2d.
/frameworks/base/test-runner/src/android/test/AndroidTestRunner.java
|
12093976a4842a795491cfd2b1d3b71e18503f2d |
|
19-Feb-2010 |
Brett Chabot <brettchabot@android.com> |
Move framework test-runner unit tests to be closer to their source. Move the test-runner source into a separate src folder to accommodate the test move.
/frameworks/base/test-runner/src/android/test/AndroidTestRunner.java
|