[ 
https://issues.apache.org/jira/browse/OFBIZ-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966220#comment-14966220
 ] 

Ruud Griepsma commented on OFBIZ-6618:
--------------------------------------

Since the patch was submitted the test framework has been further developed and 
used by testers and also been made compatible for automatic execution on 
systems without a GUI (using Jenkins). The error you're getting in point 3 is 
because it's trying to use the Linux binary Chrome driver. To make it work with 
Windows, easiest is to make sure Firefox is installed on your system, then 
change the /config/selenium.properties file, disable the chrome driver and 
display variables (these are for use on systems without a GUI) and enable the 
Firefox driver. Like this: 

#driver.type=chrome
#display=:1.5

driver.type=firefox
#display=:99

I just tested it on Windows, with these settings it works for me. The 
README.TXT file is now updated in the Git repository to reflect this and the 
default driver is changed back to Firefox.

I have included your patch in the build.xml file. It works, but I had to change 
the folder to the patch directory so it could find the patches.

As Hans said, currently the testing framework is being actively developed and 
tested, once it's more mature it would indeed make sense to include it with 
Ofbiz.

> Selenium test integration using XML files
> -----------------------------------------
>
>                 Key: OFBIZ-6618
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-6618
>             Project: OFBiz
>          Issue Type: Test
>          Components: framework
>            Reporter: Ruud Griepsma
>            Assignee: Hans Bakker
>            Priority: Minor
>              Labels: selenium, test, webdriver
>             Fix For: Trunk
>
>         Attachments: ModelTestSuite.patch, build.patch, test-suite.patch
>
>
> Added a new type of test, for testing with Selenium WebDriver, but without 
> writing any Java code. This will help making GUI tests quicker and easier to 
> create. Test steps and instances are defined in XML files, like example 
> below, which tests the login procedure for the admin user.
> {code}
> <testcase>
>   <step function="openBrowser" datavalue="Firefox"/>
>   <step function="navigate" 
> datavalue="https://localhost:8443/example/control/checkLogin/main"/>
>   <step function="writeInput" by="name" webobject="USERNAME" 
> dataname="username"/>
>   <step function="writeInput" by="name" webobject="PASSWORD" 
> dataname="password"/>
>   <step function="click" by="cssSelector" 
> webobject="input[type=&quot;submit&quot;]"/>
>   <step function="checkExists" by="linkText" datavalue="Logout"/>
>   <step function="pause" datavalue="2"/>
>   <step function="closeBrowser"/>
>   
>   <testinstance>
>     <data name="username" value="admin"/>
>     <data name="password" value="ofbiz"/>
>   </testinstance>
> </testcase>
> {code}
> Git repository with example (put in 'hot-deploy' folder and check README.txt 
> file):
> git clone https://gerrit.antwebsystems.com/growerptest



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to