[JBoss JIRA] (ARQGRA-274) The request guard does timeout for delayed requests
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-274?page=com.atlassian.jira.plugin... ]
Jan Papousek updated ARQGRA-274:
--------------------------------
Priority: Critical (was: Major)
> The request guard does timeout for delayed requests
> ---------------------------------------------------
>
> Key: ARQGRA-274
> URL: https://issues.jboss.org/browse/ARQGRA-274
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.0.0.Alpha3
> Reporter: Bernard Labno
> Assignee: Jan Papousek
> Priority: Critical
> Fix For: 2.0.0.Alpha5
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In RichFaces, there is request queue which can delay a processing of an user action which avoids overwhelming communication channel.
> This is simply the case where request guard should:
> * wait specified timeout (by default type "Ajax" timeout) for user action to start AJAX request (xhr.open)
> * then wait another timeout (by default type "Ajax" timeout) for AJAX action to complete the request (xhr.readyState == 4)
--
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
12 years, 11 months
[JBoss JIRA] (ARQGRA-274) The request guard does timeout for delayed requests
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-274?page=com.atlassian.jira.plugin... ]
Jan Papousek commented on ARQGRA-274:
-------------------------------------
I found a critical bug (using Bernard's tests).
I've rewritten the Bernard's onchange test, but if fails on the commented line.
{code}
@Test
public void onChange()
{
browser.get(deploymentUrl + "noPoll.jsf");
try {
guardAjax(inputA).sendKeys("Any");
} catch (RequestGuardException e) {
fail("Unexpected RequestGuardException");
}
inputB.sendKeys("Anything");
guardAjax(serverDate).click(); //blur => it doesn't lead to the request => FAIL
}
{code}
Slightly modified test works:
{code}
@Test
public void onChangeWithReload()
{
browser.get(deploymentUrl + "noPoll.jsf");
try {
guardAjax(inputA).sendKeys("Any");
} catch (RequestGuardException e) {
fail("Unexpected RequestGuardException");
}
browser.get(deploymentUrl + "noPoll.jsf"); // refresh
inputB.sendKeys("Anything");
guardAjax(serverDate).click(); //blur => OK
}
{code}
Use https://github.com/papousek/graphene-guard-test for reproduction.
> The request guard does timeout for delayed requests
> ---------------------------------------------------
>
> Key: ARQGRA-274
> URL: https://issues.jboss.org/browse/ARQGRA-274
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.0.0.Alpha3
> Reporter: Bernard Labno
> Assignee: Jan Papousek
> Fix For: 2.0.0.Alpha5
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In RichFaces, there is request queue which can delay a processing of an user action which avoids overwhelming communication channel.
> This is simply the case where request guard should:
> * wait specified timeout (by default type "Ajax" timeout) for user action to start AJAX request (xhr.open)
> * then wait another timeout (by default type "Ajax" timeout) for AJAX action to complete the request (xhr.readyState == 4)
--
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
12 years, 11 months
[JBoss JIRA] (ARQGRA-274) The request guard does timeout for delayed requests
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-274?page=com.atlassian.jira.plugin... ]
Work on ARQGRA-274 stopped by Jan Papousek.
> The request guard does timeout for delayed requests
> ---------------------------------------------------
>
> Key: ARQGRA-274
> URL: https://issues.jboss.org/browse/ARQGRA-274
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.0.0.Alpha3
> Reporter: Bernard Labno
> Assignee: Jan Papousek
> Fix For: 2.0.0.Alpha5
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In RichFaces, there is request queue which can delay a processing of an user action which avoids overwhelming communication channel.
> This is simply the case where request guard should:
> * wait specified timeout (by default type "Ajax" timeout) for user action to start AJAX request (xhr.open)
> * then wait another timeout (by default type "Ajax" timeout) for AJAX action to complete the request (xhr.readyState == 4)
--
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
12 years, 11 months
[JBoss JIRA] (ARQGRA-274) The request guard does timeout for delayed requests
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-274?page=com.atlassian.jira.plugin... ]
Work on ARQGRA-274 started by Jan Papousek.
> The request guard does timeout for delayed requests
> ---------------------------------------------------
>
> Key: ARQGRA-274
> URL: https://issues.jboss.org/browse/ARQGRA-274
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.0.0.Alpha3
> Reporter: Bernard Labno
> Assignee: Jan Papousek
> Fix For: 2.0.0.Alpha5
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In RichFaces, there is request queue which can delay a processing of an user action which avoids overwhelming communication channel.
> This is simply the case where request guard should:
> * wait specified timeout (by default type "Ajax" timeout) for user action to start AJAX request (xhr.open)
> * then wait another timeout (by default type "Ajax" timeout) for AJAX action to complete the request (xhr.readyState == 4)
--
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
12 years, 11 months
[JBoss JIRA] (ARQGRA-279) Support for method Graphene.element(WebElement, By) and its condition isPresent
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-279?page=com.atlassian.jira.plugin... ]
Jan Papousek resolved ARQGRA-279.
---------------------------------
Resolution: Done
resolved by this commit: https://github.com/arquillian/arquillian-graphene/commit/006d90d75d8b480f...
> Support for method Graphene.element(WebElement, By) and its condition isPresent
> -------------------------------------------------------------------------------
>
> Key: ARQGRA-279
> URL: https://issues.jboss.org/browse/ARQGRA-279
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Components: api
> Reporter: Sona Jamborova
> Assignee: Jan Papousek
> Fix For: 2.0.0.Alpha5
>
>
> Please, can you add support for method Graphene.element(WebElement, By) for searching element (located by By) in parent element.
> Motivation:
> A panel which display content of current directory. Operations with this panel are open a file, open a child directory, go back. The content of this panel depends on file system and we use different file system for our test. I need create general framework for our tests. I think about:
> {code}
> public class Designer {
> ...
> @FindBy(jquery = "div.tabbable:contains('Project Explorer')")
> private ProjectExplorer projExpl;
> ...
> }
> {code}
> {code}
> public class ProjectExplorer {
> ...
> @Root
> private WebElement root;
>
> @FindBy(css = "table>tr:first-child() div");
> private WebElement path;
> ...
>
> public void openFile(String path) {
> String[] parts = path.split("/");
> for (String part: parts) {
> By by = jquerySelector(format("a.gwt-Anchor:contains('%s')", part));
> waitAjax().until(element(root, by).isPresent());
> root.findElement(by).click(); //this should be reduce to waitAjax().until(element(root, by).isPresent()).click(); (this is not point of this issue)
> }
> }
> public String getPath () {
> return path.getText();
> }
> }
> {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
12 years, 11 months
[JBoss JIRA] (ARQGRA-279) Support for method Graphene.element(WebElement, By) and its condition isPresent
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-279?page=com.atlassian.jira.plugin... ]
Jan Papousek updated ARQGRA-279:
--------------------------------
Sprint: Sprint 1
> Support for method Graphene.element(WebElement, By) and its condition isPresent
> -------------------------------------------------------------------------------
>
> Key: ARQGRA-279
> URL: https://issues.jboss.org/browse/ARQGRA-279
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Components: api
> Reporter: Sona Jamborova
> Assignee: Jan Papousek
> Fix For: 2.0.0.Alpha5
>
>
> Please, can you add support for method Graphene.element(WebElement, By) for searching element (located by By) in parent element.
> Motivation:
> A panel which display content of current directory. Operations with this panel are open a file, open a child directory, go back. The content of this panel depends on file system and we use different file system for our test. I need create general framework for our tests. I think about:
> {code}
> public class Designer {
> ...
> @FindBy(jquery = "div.tabbable:contains('Project Explorer')")
> private ProjectExplorer projExpl;
> ...
> }
> {code}
> {code}
> public class ProjectExplorer {
> ...
> @Root
> private WebElement root;
>
> @FindBy(css = "table>tr:first-child() div");
> private WebElement path;
> ...
>
> public void openFile(String path) {
> String[] parts = path.split("/");
> for (String part: parts) {
> By by = jquerySelector(format("a.gwt-Anchor:contains('%s')", part));
> waitAjax().until(element(root, by).isPresent());
> root.findElement(by).click(); //this should be reduce to waitAjax().until(element(root, by).isPresent()).click(); (this is not point of this issue)
> }
> }
> public String getPath () {
> return path.getText();
> }
> }
> {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
12 years, 11 months