Metamer - design tests for key events in trees
----------------------------------------------
Key: RFPL-1124
URL: https://issues.jboss.org/browse/RFPL-1124
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QE
Affects Versions: 4.0.0.Milestone6
Reporter: Lukas Fryc
Assignee: Lukas Fryc
Fix For: 4.0.0.Final
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Autocomplete test automation - selection/confirmation by mouse
--------------------------------------------------------------
Key: RFPL-929
URL: https://jira.jboss.org/browse/RFPL-929
Project: RichFaces Planning
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: QA
Affects Versions: 4.0.0.Milestone4
Reporter: Lukas Fryc
Assignee: Lukas Fryc
Fix For: Future_4.X
Currently, there are only basic tests to test autocomplete using keys - use similar scenarios in test cases using mouse.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Metamer: rich:dataTable filtering example broken table header layout
--------------------------------------------------------------------
Key: RFPL-1790
URL: https://issues.jboss.org/browse/RFPL-1790
Project: RichFaces Planning
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.Milestone4
Environment: RichFaces 4.1.0.20111101-M4
Metamer 4.1.0.20111101-M4 r.22863
Mojarra 2.1.3-SNAPSHOT
Apache Tomcat 7.0.22
Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
Chrome 14.0.835.202 @ Linux i686
Reporter: Ján Jamrich
Assignee: Ján Jamrich
Filtering controls in table header have broken layout. For more info see screenshot attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Metamer - Introduce New Templates
---------------------------------
Key: RFPL-942
URL: https://jira.jboss.org/browse/RFPL-942
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QA
Reporter: Lukas Fryc
Assignee: Lukas Fryc
Fix For: 4.0.0.Final
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Metamer - Templates - introduce template for testing dataScroller
-----------------------------------------------------------------
Key: RFPL-944
URL: https://jira.jboss.org/browse/RFPL-944
Project: RichFaces Planning
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: QA
Reporter: Lukas Fryc
Assignee: Pavol Pitonak
Fix For: 4.0.0.CR1
Template should show the second or subsequent page of the table.
Consider connection with showing component sample in second column/row RFPL-942
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
RichFaces testing with Android
------------------------------
Key: RFPL-1540
URL: https://issues.jboss.org/browse/RFPL-1540
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QE
Affects Versions: 4.0.0.Final
Reporter: Pavol Pitonak
Assignee: Juraj Huska
Fix For: 4.1.0.Final
Prepare QE environment for automated testing of RichFaces 4.1.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
CLONE - Prep content, and contact internal/external sources for publication
---------------------------------------------------------------------------
Key: RFPL-1933
URL: https://issues.jboss.org/browse/RFPL-1933
Project: RichFaces Planning
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: administration
Reporter: Jay Balunas
Assignee: Jay Balunas
Fix For: 4.0.0.Final
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira