[arquillian-issues] [JBoss JIRA] (ARQGRA-377) Improve the conditions API

[Marek Schmidt (JIRA)]

    [ https://issues.jboss.org/browse/ARQGRA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804441#comment-12804441 ] 

Marek Schmidt commented on ARQGRA-377:
--------------------------------------

We can maybe also just have e.g. condition()  to "realize" the fluidum:

if (condition().element(webElementOrBy).is().not().present()) {
 ...
}

so one piece of the same code can be used in both waits and conditions, which I believe is the core of this usability issue.
                
> Improve the conditions API
> --------------------------
>
>                 Key: ARQGRA-377
>                 URL: https://issues.jboss.org/browse/ARQGRA-377
>             Project: Arquillian Graphene
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 2.0.0.Beta1
>            Reporter: Juraj Húska
>
> Currently the conditions API looks like:
> {code}
> new WebElementConditionFactory(webElement).isEnabled().apply(webDriverInstance);{code}
> It should be improved to be more concise.
> Consider inspiring with *hamcrest* library ([link|https://code.google.com/p/hamcrest/]), which should allow to have conditions API like:
> {code}
> import static foo.bar.Matchers.*;
> public void testEquals() {
>     WebElement element = browser.findBy(By.tagName("body"));
>     assertThat(element, isDisplayed());
> }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira