Class DateTimePickerTester
-
- All Implemented Interfaces:
-
com.vaadin.browserless.Clickable
public class DateTimePickerTester<T extends DateTimePicker> extends ComponentTester<T>
Tester for DateTimePicker components.
- Since:
1.0
-
-
Constructor Summary
Constructors Constructor Description DateTimePickerTester(T component)Wrap given component for testing.
-
Method Summary
Modifier and Type Method Description voidsetValue(LocalDateTime dateTime)Set the date to the component, as the user would enter it. booleanisValid()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 com.vaadin.flow.data.binder.Binder or a custom validator does. voidclear()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
-
DateTimePickerTester
DateTimePickerTester(T component)
Wrap given component for testing.
- Parameters:
component- target component
-
-
Method Detail
-
setValue
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.- Parameters:
dateTime- date time to set to component
-
isValid
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 com.vaadin.flow.data.binder.Binder or a custom validator does.
A field can hold a value that does not satisfy its constraints — the user can type one, setValue 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.
- Returns:
trueif the field is not marked invalid and its current value satisfies the constraints of the field- Since:
25.3
-
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.- Since:
25.3
-
-
-
-