Last Updated: 23 August 2024 | Change Log

AccessCheckoutEditText

Important

To ensure you remain SAQ-A compliant, the AccessCheckoutEditText component has been designed to not expose any methods or properties to retrieve the text entered by the end user.

You can customize your views. Here are the methods and properties supported by our component:

XML Properties

In addition to the XML supported by the View class, here are the properties supported by our component:

NameType
android:textColorColor
android:hintString
android:textColorHintColor
android:imeOptionsInt
android:cursorVisibleBoolean
android:textSizeFloat
android:fontTypeface

Methods

In addition to the View class, here are the methods supported by our component:

Methods
getHint():CharSequence
setHint(value:CharSequence)
isEnabled():Boolean
setEnabled(value:Boolean)
getCurrentTextColor():Int
setTextColor(value:Int)
getCurrentHintTextColor():Int
setHintColor(value:Int)
getImeOptions():Int
setImeOptions(value:Int)
getTextSize():Float
setTextSize(value:Float)
getTypeface():Typeface
setTypeFace(value:Typeface)
isCursorVisible():Boolean
setCursorVisible(value:Boolean)
setText(text:String)
clear()

There are methods from the view class which are not supported, these are:

Methods not supported
getBackgroundTintList():ColorStateList
setBackgroundTintMode(PorterDuff.Mode tintMode)
setBackgroundTintBlendMode(BlendMode blendMode)

Use Espresso for UI Testing

AccessCheckoutEditText acts as a wrapper around an EditText. This is to ensure you can't access the EditText instance and remain SAQ-A compliant.

Because of this, you must perform an action on the EditText rather than on the AccessCheckoutEditText instance.

You can access the EditText instance in Espresso by using the code below, where the id corresponds to the id of the AccessCheckoutEditText instance:

Espresso.onView(ViewMatchers.withParent(withId(R.id.your_identifier)))