[
https://issues.apache.org/jira/browse/OFBIZ-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharan Foga updated OFBIZ-3438:
-------------------------------
Sprint: Bug Crush Event - 21/2/2015
> Migrate from DefaultSelenium to HttpCommandProcessor
> ----------------------------------------------------
>
> Key: OFBIZ-3438
> URL: https://issues.apache.org/jira/browse/OFBIZ-3438
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
> Affects Versions: Trunk
> Reporter: Erwan de FERRIERES
> Priority: Minor
> Attachments: OFBIZ-3438.patch
>
>
> seleniumXml is using the DefaultSelenium class. This class always returns
> void, and then logging on it is not possible. The HttpCommandProcessor is
> used to send and receive information from the selenium server via HTTP
> requests, and returns a OK or ERROR message as a result. Therefore, logging
> can be enabled, and screenshots can be triggered when an error occurs.
> I've started the migration, but I'm running out of time at the moment.
> The attached patch has the modification I have already done, and test are
> launched via the selenium dedicated page
> (https://localhost:8443/webtools/control/selenium), and running the
> commeventopportunity_testsuite, which contains an error
> This JIRA is intended to be used by anyone who wants to improve the
> seleniumXML logging usage, and any contribution would be really appreciated!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
