[richfaces-planning-issues] [JBoss JIRA] (RFPL-3038) RF5 Charts: Initial QE Tasks

[Matej Novotny (JIRA)]

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

Matej Novotny commented on RFPL-3038:
-------------------------------------

Since we moved this to 4.5 release this issue is still relevant and I forgot to update it.

So here is what we have covered:
* Charts (as we tested them in Alpha3) were fully working for desktops and disabled for mobiles
* Framework [tests|https://github.com/richfaces/richfaces/blob/master/components/rich/src/test/integration/org/richfaces/component/chart/ITChartBasic.java] are done
* Metamer has [charts samples|https://github.com/richfaces/richfaces-qa/tree/master/metamer/application/src/main/webapp/components/richChart] as well as additional tests
* Jenkins job cam be run as long as Chrome is used, tests are marked as Smoke
** This is due to a Selenium issue with clicking on canvas (offset is not taken into account while targeting canvas)

And what we need to take a look at:
* Page fragment
** We don't have one
** IMHO it does not make much sense to create one as the component is based on flotr charts which have a full size JS API
** As of now there is not much interaction with charts which could be exported into fragment methods
** [~ppitonak] do you think it makes sense to create a fragment?
* Documentation
** Haven't inspected this much yet, I will take a closer look at it

> RF5 Charts: Initial QE Tasks
> ----------------------------
>
>                 Key: RFPL-3038
>                 URL: https://issues.jboss.org/browse/RFPL-3038
>             Project: RichFaces Planning
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: QE
>    Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha2
>            Reporter: Pavol Pitonak
>            Assignee: Matej Novotny
>            Priority: Critical
>             Fix For: 4.5-Tracking
>
>
> # review chart components
> # create JavaScript tests for chart components
> # create/update Jenkins job to run JavaScript tests continuously
> # add chart components to Metamer (on feature branch as long as they are in sandbox)
> # create page fragment if it makes sense
> # create framework tests for chart components 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
> link all reported bugs in component to this issue



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)