[JBoss JIRA] (RFPL-3267) Create tests for stateless views
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RFPL-3267?page=com.atlassian.jira.plugin.... ]
Jiří Štefek updated RFPL-3267:
------------------------------
Fix Version/s: 5.0.0.Alpha4
> Create tests for stateless views
> --------------------------------
>
> Key: RFPL-3267
> URL: https://issues.jboss.org/browse/RFPL-3267
> Project: RichFaces Planning
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: QE
> Reporter: Matej Novotny
> Assignee: Jiří Štefek
> Labels: jsf22
> Fix For: 5.0.0.Alpha4
>
>
> Based on RFPL-2506, we need to test that our components work with _stateless views_ which were introduced in JSF 2.2.
> We could probably reuse test pages from Metamer with just some tempering.
> For more information on _stateless views_ see [this|http://jdevelopment.nl/jsf-22/#1055] page.
--
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
10 years, 2 months
[JBoss JIRA] (RFPL-3269) RF5 Editor: Initial QE Tasks
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RFPL-3269?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak updated RFPL-3269:
--------------------------------
Fix Version/s: 5.0.0.Alpha4
(was: 5-Future)
> RF5 Editor: Initial QE Tasks
> ----------------------------
>
> Key: RFPL-3269
> URL: https://issues.jboss.org/browse/RFPL-3269
> Project: RichFaces Planning
> Issue Type: Task
> Security Level: Public(Everyone can see)
> 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 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
10 years, 2 months
[JBoss JIRA] (RFPL-3268) Reimplement MatrixConfigurator in Metamer tests
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RFPL-3268?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak updated RFPL-3268:
--------------------------------
Fix Version/s: 5.0.0.Alpha4
(was: 5-Future)
> Reimplement MatrixConfigurator in Metamer tests
> -----------------------------------------------
>
> Key: RFPL-3268
> URL: https://issues.jboss.org/browse/RFPL-3268
> Project: RichFaces Planning
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: QE
> Reporter: Pavol Pitonak
> Assignee: Jiří Štefek
> Fix For: 5.0.0.Alpha4
>
>
> Metamer component enabling us to run tests in various templates and to run tests with parameters.
> Problems of current implementation:
> * Implemented as a TestNG interceptor, i.e. it cannot work with JUnit (which is used by all other RichFaces tests)
> * We cannot upgrade to latest version of TestNG (not sure why, probably a bug in TestNG interceptors, it skips tests)
> Requirements for new implementation (almost identical to current implementation):
> * It should work with both TestNG and JUnit (preferably implemented as an Arquillian extension)
> * I can run tests in plain template: mvn clean verify
> * I can run tests in all templates: mvn clean verify -Dtemplates=*
> * I can run tests in all templates using "all" (asterisk cannot be used in Jenkins matrix): mvn clean verify -Dtemplates=all
> * I can run tests in one specific template: mvn clean verify -Dtemplates=richList
> * I can run tests in two or more specific templates (each separately): mvn clean verify -Dtemplates=richList,richDataTable, i.e. each test will run twice - once in richList template and once in richDataTable template
> * I can run tests in two or more specific templates (applied all at once): mvn clean verify -Dtemplates=richList,richDataTable, i.e. each test will run once - with both richList and richDataTable templates activated concurently, comma cannot be used as separator - optional feature?
> * I can configure a test class/method to run with specific templates using @Templates (as is now)
> * I can configure a test class/method not to run with specific templates using @Templates (as is now)
> * I can configure a test to run with multiple parameters using @Inject, @Use (as is now)
--
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
10 years, 2 months
[JBoss JIRA] (RFPL-3271) Remove JMS from Metamer
by Pavol Pitonak (JIRA)
Pavol Pitonak created RFPL-3271:
-----------------------------------
Summary: Remove JMS from Metamer
Key: RFPL-3271
URL: https://issues.jboss.org/browse/RFPL-3271
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
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.0.0 and EAP 6.2.1
## create new Jenkins job for these tests
# verify that remaining r:push tests in Metamer still work
--
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
10 years, 2 months
[JBoss JIRA] (RFPL-3269) RF5 Editor: Initial QE Tasks
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RFPL-3269?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak updated RFPL-3269:
--------------------------------
Description:
# 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.
was:
# 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
> RF5 Editor: Initial QE Tasks
> ----------------------------
>
> Key: RFPL-3269
> URL: https://issues.jboss.org/browse/RFPL-3269
> Project: RichFaces Planning
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: QE
> Reporter: Pavol Pitonak
> Assignee: Matej Novotny
> Priority: Blocker
> Fix For: 5-Future
>
>
> # 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 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
10 years, 2 months