Class BigDecimalFieldLocator
java.lang.Object
com.vaadin.browserless.locator.Locator<BigDecimalField,BigDecimalFieldLocator>
com.vaadin.flow.component.textfield.BigDecimalFieldLocator
- All Implemented Interfaces:
Clickable<BigDecimalField>,HasAriaLabelFilter<BigDecimalField,,BigDecimalFieldLocator> HasLabelFilter<BigDecimalField,,BigDecimalFieldLocator> HasPlaceholderFilter<BigDecimalField,,BigDecimalFieldLocator> HasThemeFilter<BigDecimalField,,BigDecimalFieldLocator> HasValueFilter<BigDecimalField,BigDecimal, BigDecimalFieldLocator>
@Generated("com.vaadin.browserless.locator.processor.LocatorProcessor")
public class BigDecimalFieldLocator
extends Locator<BigDecimalField,BigDecimalFieldLocator>
implements Clickable<BigDecimalField>, HasLabelFilter<BigDecimalField,BigDecimalFieldLocator>, HasAriaLabelFilter<BigDecimalField,BigDecimalFieldLocator>, HasPlaceholderFilter<BigDecimalField,BigDecimalFieldLocator>, HasValueFilter<BigDecimalField,BigDecimal,BigDecimalFieldLocator>, HasThemeFilter<BigDecimalField,BigDecimalFieldLocator>
Generated locator for
BigDecimalField, derived from
TextFieldTester. 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 Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoidclear()Empties the field, as when the user deletes its contents (or clicks the clear button, where one is shown).voidEmpties the field by clicking its clear button, as the user would.voidEnsures the component is in a usable state before interaction.Gets the component being tested.voidsetValue(BigDecimal value) Set the given value for the component, as the user would type it.Methods inherited from class com.vaadin.browserless.locator.Locator
atIndex, component, components, exists, inside, inside, invalidate, self, with, withAttribute, withAttribute, withClassName, withCondition, withId, withinSlot, withoutAttribute, withoutAttribute, withoutClassName, withTestIdMethods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface com.vaadin.browserless.Clickable
click, click, click, middleClick, middleClick, rightClick, rightClickMethods inherited from interface com.vaadin.browserless.locator.HasAriaLabelFilter
withAriaLabel, withAriaLabelContainingMethods inherited from interface com.vaadin.browserless.locator.HasLabelFilter
withLabel, withLabelContainingMethods inherited from interface com.vaadin.browserless.locator.HasPlaceholderFilter
withPlaceholder, withPlaceholderContainingMethods inherited from interface com.vaadin.browserless.locator.HasThemeFilter
withoutTheme, withoutTheme, withTheme, withThemeMethods inherited from interface com.vaadin.browserless.locator.HasValueFilter
withValue
-
Constructor Details
-
BigDecimalFieldLocator
public BigDecimalFieldLocator() -
BigDecimalFieldLocator
-
-
Method Details
-
getComponent
Description copied from interface:ClickableGets the component being tested.- Specified by:
getComponentin interfaceClickable<BigDecimalField>- Returns:
- the component under test
-
ensureComponentIsUsable
public void ensureComponentIsUsable()Description copied from interface:ClickableEnsures the component is in a usable state before interaction.- Specified by:
ensureComponentIsUsablein interfaceClickable<BigDecimalField>
-
setValue
Set the given value for the component, as the user would type it. A value that only breaks a validation constraint ? shorter than minLength, not matching pattern, 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 withHasValidation.isInvalid()instead of expecting this method to throw. A value the user physically cannot type is refused: the browser truncates what is over maxLength and filters out the keystrokes allowedCharPattern does not match, so a longer value or a disallowed character fails with anIllegalArgumentException. So doesnullon a field whose empty value is notnull, as a text input has no null state ? emptying the field isclear(). Javadoc copied fromTextFieldTester.setValue(java.lang.Object).- Parameters:
value- value to set- Throws:
IllegalStateException- if the component is not usableIllegalArgumentException- if the value is one the user could not have typed
-
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 fromTextFieldTester.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. Unlikeclear(), 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 fromTextFieldTester.clickClearButton().- Throws:
IllegalStateException- if the component is not usable, or its clear button is not visible
-