Devices on test benches are usually held sideways, which leads to app
rotation during launch. While it's useful to identify such issue from an
app perspective, the app compatibility test should be isolated from such
noise for the purpose of the testing for basic level of compatibility.
Change-Id: I403f96e5d8512ca6a17b05a83d69f4b02f760a32
Some apks includes widgets and does not have a launchable
activity. The inclusion of such apk for launching is an issue
with test configuration, not test failure.
Also logging intent used for app package for debugging purpose.
Change-Id: Ibca05757a401ea036e9910d8580d7cafd356567c
decide if the app is still running after launch by checking
running tasks and look for a task with base activity belonging
to the package launched.
Change-Id: Ibb3894e765ccbca62f803decc3c1c1f36dc2d454
This happens when an app is launched but has a dialog shown on
top of it. Typical reason is a licensing prompt of sorts.
Change-Id: Id73f45f54767b869873c62f13aeeb470c1a5cd81
In addition to ensuring that process exists, we also need to
check that it's the right state. Because crashed foreground
activity can still get started as background service.
Bug: 20899208
Change-Id: I101e556ce757af1afb66686827c5851dd6fda620
If an app from the apk cannot be launched then skip it in compatibility
test, rather than generate a null pointer exception.
Change-Id: I252031f249bfe25282b10394889ab8c5506cabcf
