[JBoss JIRA] Created: (ARQ-216) Extensions should be able to communicate between Client and Container
by Aslak Knutsen (JIRA)
Extensions should be able to communicate between Client and Container
---------------------------------------------------------------------
Key: ARQ-216
URL: https://jira.jboss.org/browse/ARQ-216
Project: Arquillian
Issue Type: Feature Request
Components: Frameworks, Test Protocol SPIs and Implementation
Reporter: Aslak Knutsen
Arquillian should provide a Communication channel between the Container and Client so extension can push custom data between.
This is needed in cases like code coverage where data is collected in container, but reported on on the client side.
I think it should be ok to open up the TestRunner Protocols for 'custom' data as well as the TestResults. This means we can piggy back on all the Protocol impls with out much extra work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Updated: (ARQAJO-15) Implement atomic call of AjaxWaiting$waitForChangeAndReturn
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQAJO-15?page=com.atlassian.jira.plugin.... ]
Lukáš Fryč updated ARQAJO-15:
-----------------------------
Fix Version/s: Future
(was: 1.0.0.Alpha3)
> Implement atomic call of AjaxWaiting$waitForChangeAndReturn
> -----------------------------------------------------------
>
> Key: ARQAJO-15
> URL: https://issues.jboss.org/browse/ARQAJO-15
> Project: Arquillian Ajocado
> Issue Type: Feature Request
> Components: core
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Minor
> Fix For: Future
>
>
> Currently, there need to be 2 operations to run operation "waitForChangeAndReturn":
> selenium.waitForCondition(js(format("{0} != '{1}'", scriptString, oldValueString)), this.getTimeout());
> String retrieved = selenium.getEval(script);
> This idea is to implement this operation atomically in meaning of Selenium.
> It can a) made tests atomic and stable, b) improve run time a little
> All previous methods fails:
> a) call getEval evaluating doWaitForCondition followed by expression to evaluate
> b) implement own method on Selenium.prototype to call doWaitForCondition and getEval in sequence (this method also lacks the possibility of passing timeout)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months