问题
Running tests on android devices with sdk 26
causes them to fail because of the new Autofill feature that hides the fields when espresso are trying to click them.
Im running my tests on firebase test lab so I cannot disable them manually on my tests devices.
Some images:
1. Password is visible before clicking username field.
2. After clicking username field password field is hidden by this Autofill dialog:
3. After login it shows another Fill dialog:
Espresso cant click now password field since the autofill dialog is hiding my field and fail
.
Using AutofillManager#disableAutofillServices()
only disabled the #2. dialog but #3. is still there.
How to disable Autofill on test devices?
回答1:
adb shell pm disable com.google.android.gms/com.google.android.gms.autofill.service.AutofillService
This should disable the autofill service. It is same as turning off autofill service in the system settings manually. It at least worked on the emulator. But this needs root access.
Another way to disable the autofill service is to change the autofill_service
settings.
adb shell settings put secure autofill_service null
回答2:
Based on documentation, you can disable Autofill services using AutofillManager#disableAutofillServices() API:
If the app calling this API has enabled autofill services they will be disabled.
Usage:
val autofillManager: AutofillManager = context.getSystemService(AutofillManager::class.java)
autofillManager.disableAutofillServices()
You can do this in @Before
step of your test.
回答3:
I've had luck disabling autofill during Espresso tests with custom ViewActions applied whenever text is entered.
.onView(...)
.perform(
new ViewAction() {
@Override
public Matcher<View> getConstraints() {
return Matchers.any(View.class);
}
@Override
public String getDescription() {
return "Marking view not important for autofill";
}
@Override
public void perform(UiController uiController, View view) {
// Required to disable autofill suggestions during tests on API 26+
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
view.setImportantForAutofill(View.IMPORTANT_FOR_AUTOFILL_NO);
}
}
})
.perform(click())
.perform(clearText())
.perform(typeText(textToType))
.perform(
new ViewAction() {
@Override
public Matcher<View> getConstraints() {
return Matchers.any(View.class);
}
@Override
public String getDescription() {
return "Dismissing autofill picker";
}
@Override
public void perform(UiController uiController, View view) {
// Required to dismiss the autofill picker during tests on API 26+
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
AutofillManager autofillManager =
view.getContext()
.getSystemService(AutofillManager.class);
if (autofillManager != null) autofillManager.cancel();
}
}
});
回答4:
An alternative code organisation based on @Alan K's solution.
Create the class DisableAutofillAction:
public class DisableAutofillAction implements ViewAction {
@Override
public Matcher<View> getConstraints() {
return Matchers.any(View.class);
}
@Override
public String getDescription() {
return "Dismissing autofill picker";
}
@Override
public void perform(UiController uiController, View view) {
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
AutofillManager autofillManager = view.getContext().getSystemService(AutofillManager.class);
if (autofillManager != null) {
autofillManager.cancel();
}
}
}
}
And, in your code when you need to disable AutoFill for editTextPassword...
editTextPassword.perform(..., ViewActions.closeSoftKeyboard(), DisableAutofillAction())
回答5:
According To Documentation : when the view is focused on and is part of a dataset. The application can be notified when the affordance is shown by registering an AutofillManager.AutofillCallback through registerCallback(AutofillCallback). When the user selects a dataset from the affordance, all views present in the dataset are autofilled, through calls to autofill(AutofillValue) or autofill(SparseArray).
The context is then finished when one of the following occurs:
- commit() is called or all savable views are gone.
- cancel() is called.
It is safe to call into its methods from any thread.
Instances of this class must be obtained using Context.getSystemService(Class) with the argument AutofillManager.class.
Use : disableAutofillServices() method to disible the service .
回答6:
The following snippet can be used to ignore the new android suggestions:
getWindow().getDecorView().setImportantForAutofill(View.IMPORTANT_FOR_AUTOFILL_NO_EXCLUDE_DESCENDANTS);
回答7:
Disable autofill when testing. Define a TestRunner class in gradle
defaultConfig {
testInstrumentationRunner "com.cover.android.TestRunner"
}
then
public class TestRunner extends AndroidJUnitRunner {
@Override
public void onCreate(Bundle arguments) {
super.onCreate(arguments);
CustomEditText.TESTING = TRUE;
}
then use a custom version of EditText
public class CustomEditText extends AppCompatEditText {
public static boolean TESTING = false;
public CustomEditText(Context context) {
super(context);
}
@Override
public int getAutofillType() {
return TESTING? AUTOFILL_TYPE_NONE : super.getAutofillType();
}
来源:https://stackoverflow.com/questions/46812716/how-to-disable-the-new-autofill-feature-from-android-oreo-for-espresso-tests