[JBoss JIRA] (ARQGRA-249) Negation in fluent API is not compilable
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-249?page=com.atlassian.jira.plugin... ]
Work on ARQGRA-249 started by Jan Papousek.
> Negation in fluent API is not compilable
> ----------------------------------------
>
> Key: ARQGRA-249
> URL: https://issues.jboss.org/browse/ARQGRA-249
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.0.0.Alpha3
> Reporter: Lukáš Fryč
> Assignee: Jan Papousek
> Fix For: 2.0.0.Alpha3
>
>
> This code is compilable:
> {code:java}
> waitGui().until().element(suggestionList).is().visible();
> {code}
> But following isn't:
> {code:java}
> waitGui().until().element(suggestionList).is().not().visible();
> {code}
> {code}
> java version "1.6.0_33"
> Java(TM) SE Runtime Environment (build 1.6.0_33-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)
> {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
11 years, 12 months
[JBoss JIRA] (ARQGRA-245) Returning a value from Function<T, V> in WebDriverwait cannot be compiled with JDK7
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-245?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-245:
------------------------------
Sprint: Sprint 2
> Returning a value from Function<T,V> in WebDriverwait cannot be compiled with JDK7
> ----------------------------------------------------------------------------------
>
> Key: ARQGRA-245
> URL: https://issues.jboss.org/browse/ARQGRA-245
> Project: Arquillian Graphene
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.0.Alpha2
> Reporter: Karel Piwko
> Assignee: Jan Papousek
> Fix For: 2.0.0.Alpha3
>
> Attachments: WebElementUntilFunction.java
>
>
> When compiling with JDK7, following error happens:
> {code}
> @FindBy(className = "failed")
> WebElement failedCasesCount;
> @FindBy(className = "passed")
> WebElement passedCasesCount;
> @FindBy(className = "total")
> WebElement totalCasesCount;
> @FindBy(id = "qunit-tests")
> QUnitResultsFragment results;
> private URL pageUrl;
> private long timeout = 60;
> private TimeUnit unit = TimeUnit.SECONDS;
> private int getExecutionResult(WebElement element) {
> if (waitModel().withTimeout(timeout, unit).until(element(element).isPresent())) {
> return Integer.valueOf(element.getText());
> }
> throw new QUnitExecutionException(MessageFormat.format(
> "Unable to execute QUnit tests at {0} within {1}{2}, timeouted.",
> pageUrl, timeout, unit));
> }
> {code}
> {code}
> [WARNING] /home/kpiwko/devel/wfk/wfk-qa/build/drone-qunit-integration/src/main/java/org/jboss/arquillian/drone/qunit/QUnitPage.java:[80,65] [unchecked] unchecked call to <V>until(Function<? super T,V>) as a member of the raw type FluentWait
> [INFO] 1 warning
> [INFO] -------------------------------------------------------------
> [INFO] -------------------------------------------------------------
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR]
> V extends Object declared in method <V>until(Function<? super T,V>)
> T extends Object declared in class FluentWait
> /home/kpiwko/devel/wfk/wfk-qa/build/drone-qunit-integration/src/main/java/org/jboss/arquillian/drone/qunit/QUnitPage.java:[80,65] error: incompatible types
> {code}
> Further investigation shows that:
> until() methods comes from Graphene
> withTimeout() comes from WebDriver
> withMessage() comes form WebDriver
> until(String) comes from Graphene and seems to be leftover from Graphene1 migration.
> The problematic part is about setting FLUENT generics to null as this cause ambiguity on JDK7.
> I'd prefer to decouple direct WebDriverWait of Graphene from WebDriverWait of WebDriver and rather use a delegate.
> That way we can create until(long,TimeUnit) or even withMessage(String), withTimeout(long,TimeUnit) methods which will be able to interfere types even on jdk7.
> Marking this issues a critical. There is no workaround how to set dynamically set wait while using Graphene on JDK7.
--
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
11 years, 12 months
[JBoss JIRA] (ARQGRA-213) print contextpath and option to sleep after starting the @Deployment
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-213?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-213:
------------------------------
Sprint: Sprint 2
> print contextpath and option to sleep after starting the @Deployment
> --------------------------------------------------------------------
>
> Key: ARQGRA-213
> URL: https://issues.jboss.org/browse/ARQGRA-213
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Reporter: Mark Struberg
> Assignee: Lukáš Fryč
> Fix For: 2.0.0.Alpha3
>
>
> Most graphene unit test have a @Deployment section and something similar to the following:
> {code}
> @ArquillianResource
> private URL contextPath;
> {code}
> When debugging the Server for finding the bug in the webapp it's often needed to manually click through the application and invoke requests directly. But to do that you need the contextpath! It would be nice if Arquillian Graphene would log this information.
> Another highly useful feature would be to stop the test after a @Deployment via a -D java option. Currently I need to add a Thread.sleep(600000L) to my test manually if I like to test the server. If I don't do that Selenium aborts the test with a failure after 30s if I'm debugging the server.
--
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
11 years, 12 months
[JBoss JIRA] (ARQGRA-249) Negation in fluent API is not compilable
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-249?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-249:
------------------------------
Sprint: Sprint 2
> Negation in fluent API is not compilable
> ----------------------------------------
>
> Key: ARQGRA-249
> URL: https://issues.jboss.org/browse/ARQGRA-249
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.0.0.Alpha3
> Reporter: Lukáš Fryč
> Assignee: Jan Papousek
> Fix For: 2.0.0.Alpha3
>
>
> This code is compilable:
> {code:java}
> waitGui().until().element(suggestionList).is().visible();
> {code}
> But following isn't:
> {code:java}
> waitGui().until().element(suggestionList).is().not().visible();
> {code}
> {code}
> java version "1.6.0_33"
> Java(TM) SE Runtime Environment (build 1.6.0_33-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)
> {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
11 years, 12 months
[JBoss JIRA] (ARQGRA-245) Returning a value from Function<T, V> in WebDriverwait cannot be compiled with JDK7
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-245?page=com.atlassian.jira.plugin... ]
Lukáš Fryč commented on ARQGRA-245:
-----------------------------------
Jan, could you please assess this issue and determine if it's something we will be able to fix in scope of {{Alpha3}}?
> Returning a value from Function<T,V> in WebDriverwait cannot be compiled with JDK7
> ----------------------------------------------------------------------------------
>
> Key: ARQGRA-245
> URL: https://issues.jboss.org/browse/ARQGRA-245
> Project: Arquillian Graphene
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.0.Alpha2
> Reporter: Karel Piwko
> Assignee: Jan Papousek
> Fix For: 2.0.0.Alpha3
>
> Attachments: WebElementUntilFunction.java
>
>
> When compiling with JDK7, following error happens:
> {code}
> @FindBy(className = "failed")
> WebElement failedCasesCount;
> @FindBy(className = "passed")
> WebElement passedCasesCount;
> @FindBy(className = "total")
> WebElement totalCasesCount;
> @FindBy(id = "qunit-tests")
> QUnitResultsFragment results;
> private URL pageUrl;
> private long timeout = 60;
> private TimeUnit unit = TimeUnit.SECONDS;
> private int getExecutionResult(WebElement element) {
> if (waitModel().withTimeout(timeout, unit).until(element(element).isPresent())) {
> return Integer.valueOf(element.getText());
> }
> throw new QUnitExecutionException(MessageFormat.format(
> "Unable to execute QUnit tests at {0} within {1}{2}, timeouted.",
> pageUrl, timeout, unit));
> }
> {code}
> {code}
> [WARNING] /home/kpiwko/devel/wfk/wfk-qa/build/drone-qunit-integration/src/main/java/org/jboss/arquillian/drone/qunit/QUnitPage.java:[80,65] [unchecked] unchecked call to <V>until(Function<? super T,V>) as a member of the raw type FluentWait
> [INFO] 1 warning
> [INFO] -------------------------------------------------------------
> [INFO] -------------------------------------------------------------
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR]
> V extends Object declared in method <V>until(Function<? super T,V>)
> T extends Object declared in class FluentWait
> /home/kpiwko/devel/wfk/wfk-qa/build/drone-qunit-integration/src/main/java/org/jboss/arquillian/drone/qunit/QUnitPage.java:[80,65] error: incompatible types
> {code}
> Further investigation shows that:
> until() methods comes from Graphene
> withTimeout() comes from WebDriver
> withMessage() comes form WebDriver
> until(String) comes from Graphene and seems to be leftover from Graphene1 migration.
> The problematic part is about setting FLUENT generics to null as this cause ambiguity on JDK7.
> I'd prefer to decouple direct WebDriverWait of Graphene from WebDriverWait of WebDriver and rather use a delegate.
> That way we can create until(long,TimeUnit) or even withMessage(String), withTimeout(long,TimeUnit) methods which will be able to interfere types even on jdk7.
> Marking this issues a critical. There is no workaround how to set dynamically set wait while using Graphene on JDK7.
--
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
11 years, 12 months