[JBoss JIRA] (RFPL-3264) Create tests for @FlowScoped annotation
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3264?page=com.atlassian.jira.plugin.... ]
Matej Novotny commented on RFPL-3264:
-------------------------------------
[~ppitonak] should we still create tests for this or is it outdated by now?
> Create tests for @FlowScoped annotation
> ---------------------------------------
>
> Key: RFPL-3264
> URL: https://issues.jboss.org/browse/RFPL-3264
> Project: RichFaces Planning
> Issue Type: Enhancement
> 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 was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 6 months
[JBoss JIRA] (RFPL-3265) Test alignment between RF templating approach and that of Resource Library Contracts
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3265?page=com.atlassian.jira.plugin.... ]
Matej Novotny commented on RFPL-3265:
-------------------------------------
[~ppitonak] is it still worth creating any kind of these tests? Or is it outdated by now?
> Test alignment between RF templating approach and that of Resource Library Contracts
> ------------------------------------------------------------------------------------
>
> Key: RFPL-3265
> URL: https://issues.jboss.org/browse/RFPL-3265
> Project: RichFaces Planning
> Issue Type: Enhancement
> Components: QE
> Reporter: Matej Novotny
> Assignee: Matej Novotny
> Labels: jsf22
>
> Based on RFPL-2506, we need to test that RF templating approach and Resource Library Contracts in JSF 2.2 work correctly together.
> The idea is that we could test Resource Library Contracts feature in combination with RF (where we turn off skinning) to see how it cooperates and whether it affects RF components and how.
> For more information on Resource Library Contracts see this [page|http://jdevelopment.nl/jsf-22/#1142].
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 6 months
[JBoss JIRA] (RFPL-3034) Run RichFaces 5 tests with JSF 2.2
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3034?page=com.atlassian.jira.plugin.... ]
Matej Novotny resolved RFPL-3034.
---------------------------------
Resolution: Out of Date
> Run RichFaces 5 tests with JSF 2.2
> ----------------------------------
>
> Key: RFPL-3034
> URL: https://issues.jboss.org/browse/RFPL-3034
> Project: RichFaces Planning
> Issue Type: Task
> Components: QE
> Affects Versions: 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Assignee: Matej Novotny
> Fix For: 5-Future
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> Smoke-test RichFaces 5 with Mojarra 2.2. The easiest way is to run existing tests on latest WildFly 8 (now 8.0.0.Alpha4). There are two Arquillian profiles ready in richfaces-qa repository (wildfly-managed-8-0 and wildfly-remote-8-0) but Metamer itself doesn't work on WildFly.
> # Fix Metamer so that it works in all containers, including WildFly 8.
> # Create Jenkins job running all Metamer tests in "plain" template with WildFly 8 on Firefox (you can copy and modify job richfaces-5.0-metamer-firefox).
> # Create wildfly-managed-8-0 and wildfly-remote-8-0 profiles in richfaces repository. Use pull request so that we can review changes.
> # Create Jenkins job running all framework tests with PhantomJS and WildFly 8 (you can copy and modify job richfaces-5.0).
> # Review all open RF issues with label "jsf22".
> # Report all problems and set label to "jsf22" on them.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 6 months
[JBoss JIRA] (RFPL-3269) RF5 Editor: Initial QE Tasks
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3269?page=com.atlassian.jira.plugin.... ]
Matej Novotny resolved RFPL-3269.
---------------------------------
Resolution: Out of Date
Resolving as out of date - this issue was to be tracked in 5.x version. In 4.5 the editor component has relevant tests.
> RF5 Editor: Initial QE Tasks
> ----------------------------
>
> Key: RFPL-3269
> URL: https://issues.jboss.org/browse/RFPL-3269
> Project: RichFaces Planning
> Issue Type: Task
> Components: QE
> Reporter: Pavol Pitonak
> Assignee: Matej Novotny
> Priority: Blocker
> Fix For: 5.0.0.Alpha4
>
>
> # review components - widget, JSF component, see demos and dev examples
> # create JavaScript tests for component
> # create/update Jenkins job(s) to run JavaScript tests continuously
> # add component to Metamer (on feature branch as long as it is in sandbox)
> # create/update page fragment if it makes sense
> # create/update framework tests for component for each component's attribute and for each major feature
> # create Metamer tests for those use-cases requiring templates
> # review documentation - JavaDoc, VDL doc, Developer Guide, Component Reference
> # update Migration Guide https://github.com/richfaces/richfaces/wiki/RichFaces-5-Migration-Guide
> Link all found issues in component to this issue.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 6 months
[JBoss JIRA] (RFPL-3271) Remove JMS from Metamer
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3271?page=com.atlassian.jira.plugin.... ]
Matej Novotny resolved RFPL-3271.
---------------------------------
Resolution: Out of Date
Resolving as out of date since this was planned for 5.x version.
> Remove JMS from Metamer
> -----------------------
>
> Key: RFPL-3271
> URL: https://issues.jboss.org/browse/RFPL-3271
> Project: RichFaces Planning
> Issue Type: Task
> Components: QE
> Affects Versions: 5.0.0.Alpha3
> Reporter: Pavol Pitonak
> Assignee: Matej Novotny
> Fix For: 5.0.0.Alpha4
>
>
> # remove JMS configuration from Metamer - remove classes JMSInitializer, JMSMessageProducer etc
> # remove JMS configuration from faces-config.xml
> # create new sample using JMS in examples/push-demo application
> ## verify that it works fine with WildFly 8.1.0 and EAP 6.2.4
> ## create new Jenkins job for these tests
> # verify that remaining r:push tests in Metamer still work
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 6 months