[
https://issues.jboss.org/browse/RFPL-2717?page=com.atlassian.jira.plugin....
]
Pavol Pitonak updated RFPL-2717:
--------------------------------
Description:
# review existing tests for each component in subtasks
# create page fragments for all components
# update existing tests to use Selenium 2 and Graphene 2, refactor them if possible
# create new tests for features that are not covered
# make all new tests run on Jenkins reliably (i.e. only tests for known open issues can
fail)
# update
http://community.jboss.org/wiki/Metamer-ComponentCoverage
Keep testng-selenium2.xml up to date. Put tests for known non-resolved issues to TestNG
group "Future".
was:
# review existing tests for each component in subtasks
# create page fragments for all components
# update existing tests to use Selenium 2 and Graphene 2, refactor them if possible
# create new tests for features that are not covered
# make all new tests run on Jenkins reliably (i.e. only tests for known open issues can
fail)
Keep testng-selenium2.xml up to date. Put tests for known non-resolved issues to TestNG
group "Future".
Migrate Metamer tests to Selenium 2 and Graphene 2
--------------------------------------------------
Key: RFPL-2717
URL:
https://issues.jboss.org/browse/RFPL-2717
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Affects Versions: 4.3.0.CR2
Reporter: Pavol Pitonak
Assignee: Ján Jamrich
Fix For: 5.0.0.M1
Original Estimate: 12 weeks
Remaining Estimate: 12 weeks
# review existing tests for each component in subtasks
# create page fragments for all components
# update existing tests to use Selenium 2 and Graphene 2, refactor them if possible
# create new tests for features that are not covered
# make all new tests run on Jenkins reliably (i.e. only tests for known open issues can
fail)
# update
http://community.jboss.org/wiki/Metamer-ComponentCoverage
Keep testng-selenium2.xml up to date. Put tests for known non-resolved issues to TestNG
group "Future".
--
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