[richfaces-planning-issues] [JBoss JIRA] Updated: (RFPL-493) richfaces-selenium - implement guards for http/xhr/no request types
Lukas Fryc (JIRA)
jira-events at lists.jboss.org
Fri Apr 2 07:04:37 EDT 2010
[ https://jira.jboss.org/jira/browse/RFPL-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Fryc updated RFPL-493:
----------------------------
Parent: RFPL-515
Security: (was: Public)
Issue Type: Sub-task (was: Task)
> richfaces-selenium - implement guards for http/xhr/no request types
> -------------------------------------------------------------------
>
> Key: RFPL-493
> URL: https://jira.jboss.org/jira/browse/RFPL-493
> Project: RichFaces Planning
> Issue Type: Sub-task
> Components: QA
> Reporter: Lukas Fryc
> Assignee: Lukas Fryc
> Fix For: 4.0.0.ALPHA2
>
>
> Task desc in following email:
> Hi,
> I'm trying to implement to our richfaces-selenium library new requirement:
> guarding what type of request will be actually done when triggering action like selenium.{click,fireEvent,type,...}.
> I identified 3 types of request used in LiveDemo:
> - XHR request
> - regular HTTP request
> - no request
> Advice needed in following:
> a) Is following access to guard XHR/HTTP requests right?
> - set the global variable like _richfaces_selenium_guard_xhr = true;
> - if it will equal undefined after triggering action, HTTP request was done, otherwise it was XHR (or no request!)
> b) how to guard that no request will be done (client-side actions) and distinguish such request from XHR?
> c) how to call regular HTTP request in API? Proposal:
> guardAjaxRequest(selenium).click(...) - XHR
> guardHttpRequest(selenium).click(...) - regular HTTP (no XHR)
> guardNoRequest(selenium).click(...) - no request
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the richfaces-planning-issues
mailing list