Re: GSoC Project update: Code and Test separation of Ofbiz and Implementing pure webdriver

Posted by Adam Heath-2 on
URL: http://ofbiz.116.s1.nabble.com/GSoC-Project-update-Code-and-Test-separation-of-Ofbiz-and-Implementing-pure-webdriver-tp3660318p3665809.html

On 07/11/2011 12:59 PM, Ganath Rathnayaka wrote:

> Hi all,
> I need all of you to know what I did up to now in my Google summer of code
> project, separating test/code of Ofbiz [1] and implementing a pure
> webdriver[2].
> I the first iteration of the summer I worked on separating test/code of
> Ofbiz. In this we were separate the three main modules,
>
>     1. applications
>     2. specialpurpose
>     3. framework
>
>
> In those modules there were submodules and some modules does not include
> java files which does not needed to do the separation. Here are the
> submodules I separated the test and code.
>
> application sub-modules
>
> accounting    manufacturing    party    workeffort
> content    marketing    product    commonext
> humanres    order    securityext
>
> specialpurpose sub-modules
>
> assetmaint  crowd    googlebase    myportal    projectmgr
> ebay    googlecheckout    oagis    shark
> cmssite    ebaystore    hhfacility    ofbizwebsite
> webpos    ecommerce    ldap    pos    workflow
>
> framework sub-modules
>
> appserver    catalina    entity    guiapp    security    webapp
> base    common    entityext    images    service    webslinger
> bi    example    jetty    sql    webtools
> birt    datafile    exampleext    minilang    start    widget
> documents    geronimo    resources    testtools
>
> After separate tests and code I had to put them as separate modules,
>
>     - src/main/java
>     - src/test/java

Er, no, do not do this.  Bad.  Stop.

Leave it as src/.  I already have stuff in ofbiz that creates
build/lib/ofbiz-base.jar and build/lib/ofbiz-base-test.jar.  There is
no reason to split the test java files out.

I actually *like* that a single javac call will compile all the code
for a component, not just the base stuff.  Makes it easier to detect
compile errors.


> This directory structure changes directly affected the building of ofbiz
> since some of the build.xml files and other files were configured to the
> older folder structure. So I have to fix them as well Erwan show me some
> places where some building exceptions and test run exceptions were came.
>
>
>     - After test/code separation of "applications", the code builded
>     successfully and ran tests successfully.
>     - After test/code separation of "specialpurpose", the code builded
>     successfully but one test failed from the "securityext" module. Find the
>     cause of this error was postponeded by Erwan since it need some work.
>     - After test/code separation of "framework", the code still not building
>     successfully. An exception thrown which we still didnt figure it out.
>
> You can find the wiki page which I logged some of my experience in [3].
>
> Also I follwed the Selenium basics which use to implementation of the
> webdriver.
>
> Plan for next iteration-
> My plans for next iteration is,
>
>     - Resolving the exception which block finishing the test/code separation
>     part.
>     - Make a plan for creating a webdriver
>     - Implementation of the webdriver
>     - Test with the newly created webdriver.
>     - Document the webdriver options.
>
>
> I must say that I was behind the timeline and I still not finish the
> test/code separation as we expected. But I believe still I can finish the
> project in time.
>
> thanks
> Ganath
>
>
> [1].https://issues.apache.org/jira/browse/OFBIZ-4211
> [2].https://issues.apache.org/jira/browse/OFBIZ-4189
> [3].
> https://cwiki.apache.org/confluence/display/OFBIZ/Code+and+test+separation+for+Apache+OFBiz
>