Package com.codeborne.selenide

Class WebElementCondition

java.lang.Object

com.codeborne.selenide.WebElementCondition

Direct Known Subclasses:

And, Animated, Attribute, AttributeWithValue, AttributeWithValue, Checked, CssClass, CssValue, CustomMatch, Disabled, Enabled, Exist, ExplainedCondition, Focused, Hidden, IsImageLoaded, MatchAttributeWithValue, NamedCondition, Not, Or, PartialValue, PseudoElementPropertyWithValue, Selected, TagName, TemporalCondition, TemporalFormatCondition, TextCondition, Value, Visible

public abstract class WebElementCondition
extends Object

Field Summary

Fields

Modifier and Type	Field	Description
protected final boolean	missingElementSatisfiesCondition
protected final String	name

Constructor Summary

Constructors

Modifier	Constructor	Description
protected	WebElementCondition(String name)
protected	WebElementCondition(String name, boolean missingElementSatisfiesCondition)

Method Summary

Modifier and Type	Method	Description
WebElementCondition	because(String message)	Should be used for explaining the reason of condition
abstract CheckResult	check(Driver driver, org.openqa.selenium.WebElement element)	Check if given element matches this condition
String	getName()
boolean	missingElementSatisfiesCondition()
WebElementCondition	negate()
WebElementCondition	or(WebElementCondition alternative)	Using "or" checks in tests is probably a flag of bad test design.
String	toString()

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Field Details

name

protected final String name

missingElementSatisfiesCondition

protected final boolean missingElementSatisfiesCondition

Constructor Details

WebElementCondition

protected WebElementCondition(String name)

WebElementCondition

protected WebElementCondition(String name,
 boolean missingElementSatisfiesCondition)

Method Details

check

@Nonnull
@CheckReturnValue
public abstract CheckResult check(Driver driver,
 org.openqa.selenium.WebElement element)

Check if given element matches this condition

Parameters:

driver - selenide driver

element - given WebElement

Returns:

CheckResult.Verdict.ACCEPT if element matches condition, or CheckResult.Verdict.REJECT if element doesn't match (and we should keep trying until timeout).

Since:

6.0.0

negate

@Nonnull
@CheckReturnValue
public WebElementCondition negate()

because

@Nonnull
@CheckReturnValue
public WebElementCondition because(String message)

Should be used for explaining the reason of condition

toString

@Nonnull
@CheckReturnValue
public String toString()

Overrides:

toString in class Object

getName

@Nonnull
@CheckReturnValue
public String getName()

missingElementSatisfiesCondition

@CheckReturnValue
public boolean missingElementSatisfiesCondition()

or

public WebElementCondition or(WebElementCondition alternative)

Using "or" checks in tests is probably a flag of bad test design. Consider splitting this "or" check into two different methods or tests.

See Also:

• NOT RECOMMENDED