Class TimePickerLocator

java.lang.Object
com.vaadin.browserless.locator.Locator<TimePicker,TimePickerLocator>
com.vaadin.flow.component.timepicker.TimePickerLocator
All Implemented Interfaces:
Clickable<TimePicker>, HasAriaLabelFilter<TimePicker,TimePickerLocator>, HasLabelFilter<TimePicker,TimePickerLocator>, HasPlaceholderFilter<TimePicker,TimePickerLocator>, HasThemeFilter<TimePicker,TimePickerLocator>, HasValueFilter<TimePicker,LocalTime,TimePickerLocator>

Generated locator for TimePicker, derived from TimePickerTester. Filter steps are inherited from Locator; action methods delegate to a fresh tester around the resolved component, so behavioral changes belong on the tester, not here.
  • Constructor Details

    • TimePickerLocator

      public TimePickerLocator()
    • TimePickerLocator

      public TimePickerLocator(TimePicker component)
  • Method Details

    • getComponent

      public TimePicker getComponent()
      Description copied from interface: Clickable
      Gets the component being tested.
      Specified by:
      getComponent in interface Clickable<TimePicker>
      Returns:
      the component under test
    • ensureComponentIsUsable

      public void ensureComponentIsUsable()
      Description copied from interface: Clickable
      Ensures the component is in a usable state before interaction.
      Specified by:
      ensureComponentIsUsable in interface Clickable<TimePicker>
    • setValue

      public void setValue(LocalTime time)
      Set the time to the component, as the user would enter it.

      A time that violates the component's constraints ? outside min - max, or the empty value on a required field ? is committed all the same, because the browser commits it too and simply leaves the field invalid. Assert that outcome with isValid() instead of expecting this method to throw. Javadoc copied from TimePickerTester.setValue(java.time.LocalTime).

      Parameters:
      time - time to set to component
      Throws:
      IllegalStateException - if the component is not usable
    • isValid

      public boolean isValid()
      Checks whether the field is currently valid, applying the same constraints as the component itself ? required, min and max ? and honouring an invalid state set from the outside, as a Binder or a custom validator does.

      A field can hold a value that does not satisfy its constraints ? the user can type one, setValue(LocalTime) commits it as the browser does, and the value can also be set on the server ? so a test asserting on validation state checks this instead of expecting a value to be refused. Javadoc copied from TimePickerTester.isValid().

      Returns:
      true if the field is not marked invalid and its current value satisfies the constraints of the field
    • clear

      public 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. Javadoc copied from TimePickerTester.clear().

      Throws:
      IllegalStateException - if the component is not usable
    • clickClearButton

      public void clickClearButton()
      Empties the field by clicking its clear button, as the user would.

      Unlike clear(), which models selecting the contents and deleting them and is therefore always available, this requires the clear button to be visible ? a hidden clear button is not something the user can click. Javadoc copied from TimePickerTester.clickClearButton().

      Throws:
      IllegalStateException - if the component is not usable, or its clear button is not visible