summaryrefslogtreecommitdiff
path: root/packages/Shell/tests/src/com/android/shell/UiBot.java
Commit message (Collapse)AuthorAgeFilesLines
* Fix BugreportReceiverTestRhed Jao2020-06-181-2/+59
| | | | | | | | | | | | | | | | - Implements a local binder and #onBind in the service to return the service instance. - Mocks BugreportManager in the service to avoid service interacting with the dumpstate. - Fixes dialog name field did not disable after service is finished. - Fixes screenshot did not remove if the name is empty. - Extends screenshot delay timeout in tests. - Fine tune the UiBot to fit new bugreport notification. - Removes obsolete cases in the tests. Bug: 143130523 Test: atest BugreportReceiverTest Change-Id: Iae89206da1d08a10891503869bbbf1ce18d4e31f
* Collapses status bar on teardown so it does not affect other tests.Felipe Leme2016-10-111-1/+1
| | | | | | | | BUG: 30639703 Test: mmm -j32 frameworks/base/packages/Shell && adb install -r -g ${ANDROID_PRODUCT_OUT}/data/app/ShellTests/ShellTests.apk && adb shell am instrument -e class com.android.shell.BugreportReceiverTest -w com.android.shell.tests/android.support.test.runner.AndroidJUnitRunner Change-Id: I2635439ac0c033d1ad6b4ba545b8d751f5576b72
* Fixed BugreportReceiverTest failures:Felipe Leme2016-08-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | - testProgress_changeJustDetailsTouchingNotification was failing because the notification mechanism changed and now provides a way to expand and collapse the actions bar, and the test was collapsing it instead of opening the details dialog. It was fixed by tapping the notification content instead of the notification title. - Similarly, openProgressNotification() was refactored to use the bugreport name instead of id. - Uses getObject() (instead of getVisibleObject()) to get the activity from the intent chooser. - Removed the redundant call to back to dismiss the keyboard, which was causing some tests to fail due to an accessibility bug. - Retry a few times in case the bugreport name system property assertion fails, since the property is set by a background thread. - Improved how notifications are canceled. - Created a sleep() helper. Besides the test case improvements, it also removed a redundant call to setCancelable() in the main code. BUG: 30641229 BUG: 30639703 Change-Id: Icd79fada22d0b8e4be034068c3e9143ef0134eed
* Always use chooser for Share Bug Report intent.Felipe Leme2016-07-281-43/+10
| | | | | | | | | When using startActivity(intent), the platform allows the user to pick the same activity for the intent, which can be a problem for sharing bug reports when the device has personal and work profiles. Change-Id: I1fd66905feb5d894307bbe5656c2aec705a59ab7 Fixes: 22115530
* Close details dialog when bugreport is canceled by user.Felipe Leme2016-07-181-2/+25
| | | | | BUG: 30158896 Change-Id: I0eab22586f6b431f2abe837088d48a655e03d213
* Fix first-time usage.Felipe Leme2016-04-151-15/+22
| | | | | | | | | When tests run for the first time, the list of activities that can handle ACTION_SEND_MULTIPLE might not be scrollable, which was cause the scrollForward() method to fail. BUG: 27431998 Change-Id: I5992bc9fec6291c74c4af7887ee66eb4f96e87c0
* Changed logic when dumpstate's max progress increases.Felipe Leme2016-03-221-3/+3
| | | | | | | | | | | | | | | | | | | | | When dumpstate starts, it estimates its maximum duration and sends it through an extra on BUGREPORT_STARTED; as it progress, it sets a system property with its current progress and if the progress value overflows the estimated max, it increases the max as well. Shell uses the max/progress to display the progress % in the system notification, and need to handle the scenario where the max changes. The initial implementation would recalculate the progress, with makes it swing back and forth as dumpstate increases the max. This CL changes the Shell logic so the progress never go back, just forward. The drawback of this approach is that if dumpstate underestimate the maximum, the progress might get stuck in a high value (99%) early on, but such issue will be addressed in the long term by tuning the estimated max value. BUG: 26354314 Change-Id: I3a5416acaffaaa43fd28d2f1f8ec8ea12aa0d91e
* Allows users to add details about a bugreport in progress.Felipe Leme2015-12-161-0/+27
| | | | | | | | | | | | | | | | | | | | The "bugreport in progress" notification now have a "DETAILS" button that when clicked opens a dialog window displaying the following fields: - Name: short name for the bugreport, will be used as part of the final files (and by default is the timestamp sent by dumpstate) - Title: a 1-line title for the bugreport, will be used as the subject in the final message. - Description: a detailed description for the bug. The main advantage of such dialog is that it allows users to enter more info about a bugreport while it's being generated, rather then when the bugreport is finished (since of the user doesn't remember what the context was when the problem happened). BUG: 25794470 BUG: 10676443 Change-Id: I0d1dba2a94ad989e541415a2a59475619a2e3d13
* Fixed ActivityChooser logic for the initial case.Felipe Leme2015-12-111-11/+10
| | | | | | | | When ActionSendMultipleConsumerActivity is not the default action, it just need to be selected, without clicking 'Just Once' BUG: 25752530 Change-Id: I111063aa0dbba37e0cac8f0572f43a48c659e975
* Improved test case by checking for dangling service.Felipe Leme2015-12-091-1/+2
| | | | | | | This check will make it easier to refactor how the bugreport is shared, which is a requirement for showing the bugreport details window. BUG: 25794470 Change-Id: If29f0515586c6680a44e0d52c4fc587808e668aa
* Improved helper used to choose an activity.Felipe Leme2015-12-031-13/+20
| | | | | | | | - Decrease delay by first checking if the activity is the default selection. - Handle scrolling so it won't fail if the activity is not visible. Change-Id: I8fce920bad207c3f35375316a139f20c1dcb9343
* Created a new bug report workflow so user can keep track of its progress.Felipe Leme2015-11-251-8/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The old workflow was: 1. dumpstate starts. 2. When dumpstate finishes, it sends a BUGREPORT_FINISHED intent. 3. Shell's BugreportReceiver receives the BUGREPORT_FINISHED and issues a system notification so user can share the bug report. The new workflow is: 1. When dumpstate starts, it sends a BUGREPORT_STARTED with its pid and the estimated total effort. 2. When Shell's BugreportReceiver receives the BUGREPORT_STARTED, it: 2.1 Issues a system notification so user can watch the progresss (which is 0% initially). 2.2 Starts a service (BugreportProgressService) responsible for polling the dumpstate progress (using system properties and the pid) and updating the system notification. 3. As dumpstate progress, it updates the proper system property. 4. When dumpstate finishes, it sends a BUGREPORT_FINISHED event. 5. When Shell's BugreportReceiver receives the BUGREPORT_FINISHED, it: 5.1 Finishes the service if necessary. 5.2 Issues a system notification so user can share the bug report. This CL handles the Shell changes only, the dumpstate changes will be changed in a separate CL. BUG: 25794470 Change-Id: Icbd0b42dd48e8db376b60544348b6818c6374338
* Initial integration test for BugReportReceiver.Felipe Leme2015-11-201-0/+130
These tests rely in the UI Automator to interact with the UI and follow the workflow below: * creates the bug report files * generates the BUGREPORT_FINISHED intent * emulate user actions to share the intent with a custom activity * asserts the extras received by the custom activity It still have some limitations, like requiring the phone to be unlocked and having the bugreport warning already checked, and those will be addressed in future CLs. BUG: 25752530 Change-Id: I01d7fad9f94daf156b728cbb9ef228bbfa6ee0f5
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-13 11:35:33 +0000