[
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