| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
See go/jetpack-test-android-migration
Exempt-From-Owner-Approval: automated package name refactoring
Test: m m -j BroadcastRadioTests KeystoreTests mediaframeworktest ActivityManagerPerfTests AppLaunch AppLaunchWear BackgroundDexOptServiceIntegrationTests AppCompatibilityTest DynamicCodeLoggerIntegrationTests FlickerLibTest InternalTests PackageWatchdogTest RcsTests RollbackTestAppAv1 RollbackTestAppAv2 RollbackTestAppACrashingV2 RollbackTestAppBv1 RollbackTestAppBv2 RollbackTestAppASplitV1 RollbackTestAppASplitV2 RollbackTest ServiceCrashTest UsageStatsPerfTests UsbTests WindowAnimationJank
Change-Id: I32fe3297656eec6060da6c7e24582bcd5315fb16
|
| |
|
|
|
|
|
|
|
| |
- reporting full dropbox content for all detected crashes leads
to overly verbose test failure message
Bug: 67002148
Test: http://sponge/4ff3ccb5-c455-45e2-9614-d3527e1f711d
Change-Id: Ic2cd2ba4ce2af0954f186b196c18cc76c19f2007
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- migrate away from deprecated JUnit3 paradigm
- scan dropbox entries for app errors, instead of probing
task list
- use IActivityController to suppress crash dialogs and record
detected app errors
- use combined dropbox and activity controller detected errors
to determine app errors
Bug: 67002148
Test: run harness against apps known to crash
Change-Id: If108cfdc7474a13e24f0d8350a7cbf99e3b51c46
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
bug: 17396762
Change-Id: I10502d5d1e2332d9e6820ee645234c125e937b7a
|
| |
|
|
| |
Change-Id: Ia9da14b8551c4ec5834a047f0792a5a213a3ac04
|
| |
|
|
| |
Change-Id: Ic30e5ee81fe6ea82e88d2c5541dc9fa9eba71043
|
| |
|
|
| |
Change-Id: I3ee02e41b835715d1b6aaf8048fbb16a6bd00b8a
|
| |
|
|
|
|
| |
Bug:8755950
Change-Id: Ie30d84cb94787d8b2e7bdc65e329a311581f4a3f
|
| |
|
|
|
|
|
| |
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
|
|
|
Change-Id: I504868ca2b7785849960be287b8d92ca3055b9ff
|