Class InputTester

    • Nested Class Summary

      Nested Classes 
      Modifier and Type Class Description
    • Field Summary

      Fields 
      Modifier and Type Field Description
      public final T component
    • Constructor Summary

      Constructors 
      Constructor Description
      InputTester(Input component) Wrap given component for testing.
    • Enum Constant Summary

      Enum Constants 
      Enum Constant Description
    • Method Summary

      Modifier and Type Method Description
      void setValue(String value) Set the value to the component if it is usable.
      String getValue() Get the current value of the component.
      void clear() Empties the field, as when the user deletes its contents (or clicks the clear button, where one is shown).
      • Methods inherited from class com.vaadin.browserless.ComponentTester

        blur, ensureComponentIsUsable, find, focus, getComponent, isFocused, isUsable, setModal
      • Methods inherited from class com.vaadin.browserless.Clickable

        click, click, click, middleClick, middleClick, rightClick, rightClick
      • Methods inherited from class java.lang.Object

        clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
    • Constructor Detail

      • InputTester

        InputTester(Input component)

        Wrap given component for testing.

        Parameters:
        component - target component
    • Method Detail

      • setValue

         void setValue(String value)

        Set the value to the component if it is usable.

        For a non interactable component an IllegalStateException will be thrown as the end user would not be able to set a value.

        Parameters:
        value - value to set
      • getValue

         String getValue()

        Get the current value of the component.

        Returns:

        current component value

      • clear

         void clear()

        Empties the field, as when the user deletes its contents (or clicks the clear button, where one is shown).

        Emptying is something the user can always do, so it needs no clear button: a field may legitimately end up invalid — a required field, for instance — once emptied.