[richfaces-planning-issues] [JBoss JIRA] Commented: (RFPL-1633) Pre-release testing of rich:editor

[Juraj Huska (JIRA)]

    [ https://issues.jboss.org/browse/RFPL-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626346#comment-12626346 ] 

Juraj Huska commented on RFPL-1633:
-----------------------------------

I am going to manually test editor in Metamer on this matrix configuration:

-containers: JBoss AS 6, JBoss AS 7
-browsers: FF 3.6.21, FF 7, Chrome 13, IE 8, IE 9



> Pre-release testing of rich:editor
> ----------------------------------
>
>                 Key: RFPL-1633
>                 URL: https://issues.jboss.org/browse/RFPL-1633
>             Project: RichFaces Planning
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: QE
>    Affects Versions: 4.1.0.Milestone2
>            Reporter: Lukáš Fryč
>            Assignee: Juraj Huska
>             Fix For: 4.1.0.Milestone2
>
>
> Editor has been greatly refactored in scope of M2 and it would be great to do release-wide testing before end of M2, this includes:
> * smoke testing of editor on all supported containers
> * complete testing of all features of editor in all supported browsers
> * smoke test with all available skins focusing on readability and usability in all supported browsers
> Please note your plan on testing matrix.
> Changes that may affect testing:
> * new 'richfaces' skin (made default)
> ** skin consistent with RichFaces component suite skins
> ** skinned main editor interface + popups
> ** popups should have consistent look with rich:popupPanel
> * configuration through {{@config}} attribute or {{<f:facet name="config">}}
> * new attributes/facets ({{skin, config, lang, ondirty}})
> [Complete list of fixed issues for editor in M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project%3DRF+and+fixVersion%3D%224.1.0.Milestone2%22+and+status+IN+%28Resolved%2C+Closed%29+AND+summary+~+editor]
> This testing should minimize the risk of introducing such fundamental changes in second milestone.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira