]
Lukáš Fryč updated ARQ-1006:
----------------------------
Fix Version/s: warp_1.next
(was: warp_1.0.0.tracking)
Warp: enriching server-triggered (push/websockets) events
---------------------------------------------------------
Key: ARQ-1006
URL:
https://issues.jboss.org/browse/ARQ-1006
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha1
Reporter: Lukáš Fryč
Fix For: warp_1.next
When testing server-side Push mechanism (like Atmosphere), the request starts on the
server (not on the client as in client-server architectures).
This is fundamentally changing how the synchronous Warp tests works:
----
We need to install the assertion pernamently on server side and filter actions we are
interested in.
Then, once the event happens, we need to transport it locally (see back-channel proposal
ARQ-1005), where we can register result of assertion and/or trigger client-side callback.
--
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: