[
https://issues.jboss.org/browse/RFPL-3264?page=com.atlassian.jira.plugin....
]
Matej Novotny commented on RFPL-3264:
-------------------------------------
[~bleathem]] I was looking into this a bit deeper and I am not sure what should be
tested.
The point of the FlowScoped bean is to preserve bean state from the beginning of the flow
to the end. If we add any component into this flow, how do we test it? I mean the
component inside the flow can surely see the bean state (that would a JSF issue not ours)
and then it can react appropriately as if it was connected to any other bean.
And even if we decided to create tests, what components should we test? We surely cannot
test all of them.
Most used pattern for flows is something as an e-shop - several pages connected together
allowing user to fill out required information and proceed to next page. As for content of
such page, it can be anything.
I might be mistaken so please correct me, but atm I cannot see clearly what is here to
test from RF point of view.
Create tests for @FlowScoped annotation
---------------------------------------
Key: RFPL-3264
URL:
https://issues.jboss.org/browse/RFPL-3264
Project: RichFaces Planning
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: QE
Reporter: Matej Novotny
Assignee: Matej Novotny
Labels: jsf22
Based on RFPL-2506, we need to create tests to verify that our components work correctly
with @FlowScoped annotation introduced in JSF 2.2.
As for test creation it would be possible to reuse a wizard use-case in Showcase
(r:togglePanel - Wizard creation), or any other similar scenario.
For more information about @FlowScoped in JSF 2.2, visit this
[page|http://jdevelopment.nl/jsf-22/#730].
--
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