Move confirmAccess method out of reader and skype workloads into
UxPerfUiAutomation base class for code reuse.
Amend project properties for reader workload to use SDK version 18.
Update jar files appropriately.
Check in missing UiAutomation .class files
Fix generation and deletion of dump sys logs including renaming to a standard [test tag]_[test number].log format
Improved Reader to run across a range of devices with subtlety different layouts and views
Moved common functionality to base classes for code reuse. Refactored
googlephotos, reader and gmail workloads to take advantage of the new
base class methods and removed total test time metric.
New methods for BaseUiAutomation:
uiDeviceVertPinchIn, uiDeviceVertPinchOut
New methods for UxPerfUiAutomation:
uiObjectVertPinchTest, writeResultsToFile, startDumpsysSurfaceFlinger,
startDumpsysSurfaceFlinger, startDumpsysGfxInfo, stopDumpsysGfxInfo
New class for UxPerfUiAutomation:
GestureTestParams
A new workload to perform standard productivity tasks within
Googlephotos. Each user event/step is timed and reported back as a
metric. Dumpsys also captures SurfaceFlinger logs for each event for
post analysis.
A new workload to perform standard productivity tasks within Reader. Each user event/step is timed and reported back as a metric. Dumpsys also captures SurfaceFlinger logs for each event for post analysis.
This extends on BaseUiAutomation to include Ux performance instrumentation and UiAutomation convenience classes.
Todo - extend the create workload infrastructure to allow you to create a new UxPerfUiAutomation workload.
The change will allow us to use UiAutomator methods introduced in API 18, such as resourceId.
As a consequence of the change all dependent uiauto workloads have been incremented also.
Tested by rebuilding all uiautomator workloads. They were not run on devices.
If uninstall fails, "pm clear" should be called to make sure that the
next time the app is launched it starts from a known state (which would
normally be ensured by the uninstall).
It's possible that there is already a version of an app on target that
differs form the version of the apk on the host. In such cases, WA will
usually try to uninstall the target version and install the host
version.
It's possible that the uninstall may fail. If that happens, it will be
reported as a warning but workload exectuion will proceed with the
target version. In this case, apk_version would have already been set to
that of the host apk. This change ensures that the APK version is
correctly set to the target version (the one that actually ran).
