ViewAction

public interface ViewAction

Known Indirect Subclasses AdapterDataLoaderAction, AtomAction<E>, CloseKeyboardAction, EditorAction, EnableJavascriptAction, GeneralClickAction, GeneralSwipeAction, KeyEventAction, OpenLinkAction, RecyclerViewActions.PositionableRecyclerViewAction, ReplaceTextAction, ScrollToAction, TypeTextAction AdapterDataLoaderAction Forces an AdapterView to ensure that the data matching a provided data matcher is loaded into the current view hierarchy.  AtomAction<E> A ViewAction which causes the provided Atom to be evaluated within a webview.  CloseKeyboardAction Closes soft keyboard.  EditorAction Performs whatever editor (IME) action is available on a view.  EnableJavascriptAction Forcibly enables Javascript on a WebView.  GeneralClickAction Enables clicking on views.  GeneralSwipeAction Enables swiping across a view.  KeyEventAction Enables pressing KeyEvents on views.  OpenLinkAction Invokes onClick of a link within a TextView (made with Linkify or via another method).  RecyclerViewActions.PositionableRecyclerViewAction Most RecyclerViewActions are given a matcher to select a particular view / viewholder within the RecyclerView.  ReplaceTextAction Replaces view text by setting EditTexts text property to given String.  ScrollToAction Enables scrolling to the given view.  TypeTextAction Enables typing text on views.

Responsible for performing an interaction on the given View element.

This is part of the test framework public API - developers are free to write their own ViewAction implementations when necessary. When implementing a new ViewAction, follow these rules:

• Inject motion events or key events via the UiController to simulate user interactions.
• Do not mutate the view directly via setter methods and other state changing methods on the view parameter.
• Do not throw AssertionErrors. Assertions belong in ViewAssertion classes.
• View action code will executed on the UI thread, therefore you should not block, perform sleeps, or perform other expensive computations.
• The test framework will wait for the UI thread to be idle both before and after perform() is called. This means that the action is guaranteed to be synchronized with any other view operations.
• Downcasting the View object to an expected subtype is allowed, so long as the object expresses the subtype matches the constraints as specified in getConstraints.

Summary

Public methods

Matcher<View> getConstraints ()

String getDescription ()

void perform (UiController uiController, 
                View view)