Age | Commit message (Collapse) | Author |
|
This makes the refreshing step explicit, and gives
users finer control.
Change-Id: Ia4b4e9476805a887096bf620d83a522d2892ee59
|
|
add optimization to SentinelScroller:
optionally start search from beginning by flinging or KEYCODE_MOVE_HOME
This seems to gain 5% speed
Change-Id: I1b303b209c5a43929314fa070398a52d776ac74a
|
|
clarify the terms of child and descendant
add XPaths.withDescendant
some cosmetic changes
Change-Id: Iaf6b7c699ccca5464db7e451d3c11715c18d4c69
|
|
Instead of inheritance by overriding matches, use composition of
a predicate.
organize imports.
Change-Id: I1aa95cb14822fb27151cda8bdffd61580b49c5e3
|
|
wait for sentinel in the corner cases when parent updates slowly
Change-Id: I9bbe36c6566dca8453ec12030d17703790ae9a25
|
|
rename PressKeyAction to SingleKeyAction
rename TypeAction to TextAction
Change-Id: I433e2fbd466143da48ab0b9d6094509560c01eca
|
|
rename Abstract* to Base*
move InputInjector to actions subpackage
Change-Id: I3e119b4052bc032f2d09d630da51b38670239da9
|
|
add UiAutomationDriver#clearAccessibilityNodeInfoCache
to work around an Accessibility bug
Change-Id: I42db1d61944240520cc34f1ccb4537f572adecf9
|
|
wait for AccessibilityEvent after injecting events
via UiAutomation
Change-Id: I3d56e07cf2e7912a21de12d1a7bacd4f33e1bc5a
|
|
clean up Events usage
revise some JavaDoc
Change-Id: Ib67fa6ecea5d7a3ef8325bc4e1778645c46d6741
|
|
add FileUtils.getAbsoluteFile
Change-Id: I278edbd60018ba230e966f5ce48cb582a98db44f
|
|
UiElement values need to be WeakReference as well
Change-Id: I31f6e833216154a3d3da7ebabc856d8ce8221631
|
|
This is compatible with other potential runners, such as G3ITR
Change-Id: I02379376c9c4a67452cf67cda5be9bc273fbc3c6
|
|
Change-Id: Ic2239d6cdf2292ea06f11596292e38d7c6755af0
|
|
Change-Id: Ic4ac93d5f9694747cb0381673cc8004ad150ea80
|
|
Change-Id: Iedc9e44e7636237488136632d8c440bc72d8ff17
|
|
Change-Id: I2ac3886656519f3ea5ae2968eb15d35fa76d8688
|
|
Change-Id: I682f2493a49db26f8092ae8bb8c5267f0c58bfc3
|
|
Change-Id: I50c4c1b10025296b70d8fc5bebcf4bfc12d41417
|
|
|
|
Previously, getVisibleBounds was only getting the coordinates of an
element relative to the topmost view, which is not the screen in the
case that there is a pop-up dialog. By using view.getLocationOnScreen,
we can adjust the relative coordinates to apply to the entire screen and
have the driver click on the correct place.
Bug: b/9743953
Change-Id: I51a2f7fc8974fba9d08c660b6e7926eb0e305abb
|
|
Change-Id: I8ada6883107d7dbceaf0e9391a683ff498924b36
|
|
Change-Id: Ib90d4058b6f3b0dca2d3ab922a045e3279eaee19
|
|
add toString for Action
Change-Id: Ib97349d1e8bb24853a1ef8856da2fb96152240c0
|
|
Change-Id: I4e317dbe742093658173a7bd2891331fbe7964de
|
|
Change-Id: Ie9c4bc52e744ccd949cc46a87b94b02ff1a549c9
|
|
Change-Id: Ic4cb68fc46cec433a7989187ed64f73e2c5aa6e8
|
|
for consistent results no matter which driver is used
Change-Id: I4f73bb194b2c652645622ba19c880fd539b74918
|
|
The problem with Music app is in DrawerLayout impl, not DroidDriver.
Also fixed logging.
Change-Id: I870dc92680708e4f9c862faa0a0618d576a9b6d8
|
|
Because UiElement.click() was performed on the center of elements, it didn't
work when the element's center was off screen. To fix this, I added a
getVisibleBounds() method to UiElement, which is implemented by ViewElement
and UiAutomationElement. This method is used in ClickAction to make sure that
the click is performed on the visible portion of the element.
DeviceUtils was added with getDisplayBounds().
Lastly, UiAutomationContext now holds Instrumentation instead of UiAutomation,
which also forced other files to change accordingly.
Change-Id: Ic2fd163a9759a0d95bd413b557976ee8a3d044f9
|
|
Change-Id: I0ff6d68be7ecc4e9f5555a32ed09aa4dd633f236
|
|
Change-Id: Ie13e6f41fc9a8783ed7ee77809b06951f7c0f8e7
|
|
Change-Id: I520f249680c72e4fa2b752de4bf4013815ff8970
|
|
Change-Id: Ie7e508d9a67629bf871d05887d26b9d3db645c32
|
|
Change-Id: I347532ed9f4e4aa59ac045a83ee7b4f25735c251
|
|
InstrumentationDriver.getRootElement"
|
|
There is now a ActivityUtils class with a getRunningActivity() method, which
depends on the overridden callActivityOnResume() and callActivityOnPause()
methods in TestRunner to maintain a currentActivity.
InstrumentationDriver.getRootElement now throws an exception if the test
activity isn't started and uses runningActivity.getWindow().getDecorView()
as the root element (used for finding elements).
Change-Id: Ib43ed5b2b8f17bc2dc20f21c24d76afe54fa34cd
|
|
Added: textContains and contentDescriptionContains (both case-
sensitive) and packageName.
Change-Id: Icd053aa330d6b55a6f9347f579038582db9f41a4
|
|
Change-Id: Id63cf416b2d548ac676e53f9377e6f7c7dbbbedf
|
|
Change-Id: I3c38997fed807af02cbd7ea9baac387d83789211
|
|
checkExists, checkGone and their variations w/ ad-hoc timeout
Change-Id: Ie742dcd04b49d044ea93b949b725736ee4ca4fe1
|
|
remove DD.getRootElement, rename DD.waitForElement to on
Change-Id: I68eef1b39889c8f1f0677fcbb265cfd9dfdca01f
|
|
move dumpDom from UiElement to DroidDriver
uniform toString in AbstractUiElement instead of subclasses
Change-Id: Ic78b812a206e73d23a47c94d9e9fe79a99c23d6c
|
|
Now both Matchers handle traversal internally
Change-Id: I368f2b60ba9e4157b7ecbef2e8f64231778a53d0
|
|
Change-Id: Ibcd6be9ea429f665a653f3aa1b3c6a27d3d84766
|
|
This follows uiautomatorviewer convention, making it
easier for DD users to use that tool.
Skip invisible children -- this is critical; e.g. ViewPager
keeps all invisible pages in memory. If users use
uiautomatorviewer to define matchers, the invisible nodes
may match surprisingly.
Change-Id: Idc4298bf18931978e2e9fd3c27e273f0e49c2f1f
|
|
This solves the clicking DrawerLayout problem, but we need to
find the exact cause to solve the general problem.
Also add logging for Events
Change-Id: I0cba140021b676cb1d13c3fe3d319c2cca535ccd
|
|
clearer logging for findElement
Change-Id: I53f4d13f6a013b97368d3f7351cffa45c7d0efe6
|
|
Change-Id: I7bb27b0f38b0bad6532eeb2470cfaeb8e6ede63f
|
|
Change-Id: I0b2f8e3876d3a3bf2111f4e44ef647a84a5bbbcd
|