00656ee81489a0e4cdc7b197d7b5ea19fac8c416 |
|
09-Mar-2017 |
Jon Mann <jonmann@google.com> |
Update rename ui tests to expect rename without name change not to fail and added a new test to verify it is a no-op. Test: fixed Bug: 35673019 Change-Id: I740882b2be2c3775c7ee32ddaf7fa9e26cb2547a
/packages/apps/DocumentsUI/tests/functional/com/android/documentsui/RenameDocumentUiTest.java
|
38f1439ce0f261b7bd4af667c087f43690f367a6 |
|
25-Jan-2017 |
Jon Mann <jonmann@google.com> |
Add more descriptive UI for conflicts while renaming. Test: updated existing rename conflict test and ran all Bug: 31647077 Change-Id: I013bb9348e4691aea42f41f58af83e18e8ca106d
/packages/apps/DocumentsUI/tests/functional/com/android/documentsui/RenameDocumentUiTest.java
|
8ff27d68c04b96f89076675de17cc268c433d5dc |
|
20-Oct-2016 |
Garfield Tan <xutan@google.com> |
Convert all LargeTest annotations to the new one. Also convert all Suppression annotations in LargetTest to the new one. It's required for our presubmit test to pass. Change-Id: Iab245d44d81b7ada8e253ba192197a8979f8157b
/packages/apps/DocumentsUI/tests/functional/com/android/documentsui/RenameDocumentUiTest.java
|
b6006b2ef723fdbb3fef3b4a350c8d363b127d0f |
|
29-Sep-2016 |
Steve McKay <smckay@google.com> |
manager/ManageActivity back to files/FilesActivity. The "mange" rename resulted in a disturbance in the force. Change-Id: I0f057ba7621912f173e47a472bfc6e23a5a6d54a
/packages/apps/DocumentsUI/tests/functional/com/android/documentsui/RenameDocumentUiTest.java
|
2567603749ff84946a888ffbd698c1381b26b5b1 |
|
19-Sep-2016 |
Garfield Tan <xutan@google.com> |
Move menu managers to respective packages. Also add some unit tests to cover mixed docs in context menus. Change-Id: I764383daed21afa5e355d85f807ad4ef1710593e
/packages/apps/DocumentsUI/tests/functional/com/android/documentsui/RenameDocumentUiTest.java
|
e5edf047145c916ac5b4696ddd7f14f5c2dbaf40 |
|
19-Sep-2016 |
Ben Lin <linben@google.com> |
Fix ContextMenuTest and RenameUiTest on Angler. When doing consecutive selections, due the fact we are using GestureDetector, consecutive selections that happen too close to each other can result it being recognized as double-clicking. By making sure "1 selected" appears first, we can wait a bit longer to make sure onSingleTapConfirmed() gets called in the code as opposed to onDoubleTap(). Bug: 31568862 Change-Id: I639b1854766d1a338b3ab397a4e6309885dba5a9
/packages/apps/DocumentsUI/tests/functional/com/android/documentsui/RenameDocumentUiTest.java
|
ae84a18a1fa5dc020fd25a963cb0955c8c31bfef |
|
16-Sep-2016 |
Steve McKay <smckay@google.com> |
Move functional tests into separate test target. Also separate out support code from unittests. Change-Id: I81490950373e170c857b23468da8d97d6aaf50d9
/packages/apps/DocumentsUI/tests/functional/com/android/documentsui/RenameDocumentUiTest.java
|