You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2015/10/23 09:33:27 UTC

[jira] [Closed] (OFBIZ-3438) Migrate from DefaultSelenium to HttpCommandProcessor

     [ https://issues.apache.org/jira/browse/OFBIZ-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques Le Roux closed OFBIZ-3438.
----------------------------------
    Resolution: Incomplete
      Assignee: Jacques Le Roux

This has been superseded by OFBIZ-6618

> 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
>            Assignee: Jacques Le Roux
>            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)