Package com.vaadin.flow.component.datetimepicker

Class DateTimePickerLocator

java.lang.Object
com.vaadin.browserless.locator.Locator<DateTimePicker,DateTimePickerLocator>
com.vaadin.flow.component.datetimepicker.DateTimePickerLocator
All Implemented Interfaces:
Clickable<DateTimePicker>, HasLabelFilter<DateTimePicker,DateTimePickerLocator>, HasThemeFilter<DateTimePicker,DateTimePickerLocator>, HasValueFilter<DateTimePicker,LocalDateTime,DateTimePickerLocator>
@Generated("com.vaadin.browserless.locator.processor.LocatorProcessor") public class DateTimePickerLocator extends Locator<DateTimePicker,DateTimePickerLocator> implements Clickable<DateTimePicker>, HasLabelFilter<DateTimePicker,DateTimePickerLocator>, HasValueFilter<DateTimePicker,LocalDateTime,DateTimePickerLocator>, HasThemeFilter<DateTimePicker,DateTimePickerLocator>
Generated locator for DateTimePicker, derived from DateTimePickerTester. 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

    • DateTimePickerLocator

      public DateTimePickerLocator()

    • DateTimePickerLocator

      public DateTimePickerLocator(DateTimePicker component)

  • Method Details

    • getComponent

      public DateTimePicker getComponent()
      Description copied from interface: Clickable
      Gets the component being tested.
      Specified by:
      getComponent in interface Clickable<DateTimePicker>
      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<DateTimePicker>

    • setValue

      public void setValue(LocalDateTime dateTime)
      Set the date to the component, as the user would enter it.

      A value 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 DateTimePickerTester.setValue(java.time.LocalDateTime).

      Parameters:
      dateTime - date 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(LocalDateTime) 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 DateTimePickerTester.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 DateTimePickerTester.clear().

      Throws:
      IllegalStateException - if the component is not usable