These tests are supposed to run even withotu @RunWith annocation, but
for better consistency we should have it there.
Bug: 110805255
Test: verified as follows. No new test failures.
tapas adb LatinIME LatinIMETests arm64 userdebug && \
DISABLE_PROGUARD=true make -j LatinIME && \
adb install -r $OUT/system/app/LatinIME/LatinIME.apk && \
atest LatinIMETests:com.android.inputmethod.latin.ContactsDictionaryUtilsTest && \
atest LatinIMETests:com.android.inputmethod.latin.ContactsContentObserverTest
Change-Id: I5c115d57b2ad41642f5f9b09b0c0d8f8c12480b0
make build uses 'shared' cert in build/make/target/product/security/.
If LatinIME APK built with AndroidStudio doesn't use the same signing
cert, then you cannot install the APK into AOSP image, which is not
convenient.
With this CL, AndroidStudio build also uses the same signing cert.
Note that shared.keystore was built as follows.
$ openssl pkcs8 -inform DER -nocrypt \
-in build/make/target/product/security/shared.pk8 \
-out shared.pem
$ openssl pkcs12 -export \
-in build/make/target/product/security/shared.x509.pem \
-inkey shared.pem -out shared.p12 \
-password pass:android -name AndroidDebugKey
$ keytool -importkeystore -deststorepass android \
-destkeystore shared.keystore -srckeystore shared.p12 \
-srcstoretype PKCS12 -srcstorepass android
Fix: 110741422
Test: made sure that the APK built with Android Studio can be
installed to an AOSP build
Change-Id: I471a87e190b15ff02bb06849e4660ed7898897a5
With this CL, you can build LatinIME and run tests for it on Android
Studio. This is still experimental and is not an official way to build
LatinIME though.
Bug: 110741422
Test: Made sure that you can build LatinIME with Android Studio
Change-Id: Ia75e3f74fa5f9b5f93dfac0b920c2e650aafa083
This CL addresses compiler warnings when building libjni_latinime.so
with NDK from Android Studio.
There should be no behavior change.
Bug: 110741422
Bug: 110757803
Test: tapas LatinIME LatinIMETests arm64 userdebug && make -j
Change-Id: Icc711dd46511a167b1fd90028552def5b2f9941f
This should be the most convenient way for both make build and Android
Studio build to share the same version code.
Bug: 110741422
Test: tapas LatinIME LatinIMETests arm64 userdebug && make -j
Change-Id: I35f850c392553b2640a4c3c7398441ac28e90eca
Host-side C++ test in LatinIME is no longer actively used and is
actually not compatible with Android Studio build.
Let's just remove this for now.
Bug: 13754552
Bug: 110741422
Test: compile
Change-Id: I3e81285fe559022e1a296051036e74d2f2afbf9c
Basically Android Studio does want targetSdkVersion to be specified in
build.gradle rather than AndroidManifest.xml. To make both make build
and Android Studio build happy, this CL splits <uses-sdk /> from the
main AndroidManifest.xml to a different file and let them merged in
make build.
There should be no behavior change.
Bug: 110741422
Test: Manually verified that there is no difference in
AndroidManifest.xml in the APK.
Change-Id: Ib673bca5a31b2f95329c9310a127ec0701bd8fdc
InstrumentationTestCase and ActivityInstrumentationTestCase2 are
deprecated. This CL rewrites tests that rely on those deprecated
classes by using Android Testing Support Library.
Bug: 110805255
Test: verified as follows. No new test failures.
tapas adb LatinIME LatinIMETests arm64 userdebug && \
DISABLE_PROGUARD=true make -j LatinIME && \
adb install -r $OUT/system/app/LatinIME/LatinIME.apk && \
atest LatinIMETests:com.android.inputmethod.keyboard.internal.MoreKeySpecStringReferenceTests LatinIMETests:com.android.inputmethod.latin.settings.AccountsSettingsFragmentTests
Change-Id: I4fefccaa0c480cfba7142ed36883da2f19b6a5f9
Yohei Yukawa
Xin Li
TreeHugger Robot
Bill Yi
android-build-team Robot