In my opinion it would be better to design the component as an independent piece of code containing: * all the jars that are required for Selenium * an ant script to run the tests (it would be nice to dynamically retrieve the tests to run from the implementationinstead of having to add configuration for each of them) * a configuration file (or mechanism) to select the Driver at runtime, the url of the server etc... * a folder containing all the automated tests available for OFBiz, categorized in some way: in my opinion, in several occasions, each functional test may span over more than one OFBiz application so it doesn't necessarily make sense to have tests split by component
In this way it will be very easy to add new tests without touching the configuration files of ootb (or custom) components: it will be an external application. Jacopo On Mar 18, 2012, at 7:23 AM, Erwan de FERRIERES wrote: > Le 18/03/2012 05:21, Kasun Siriwardhana a écrit : >> Hi Erwan, >> >> *Thanks for the reply. I had a look in to that jira issue. Does it says to >> write integration tests for entire application ? * > Hi Kasun,* > I added the wiki page, where the proposal is more explained. Please take a > look. >> *I would like to know other possibility of this ofbiz product. For an >> example a new feature implementation . Now I am going through the >> documentations on the site.* > At the moment, there is nothing more. > > Regards, > > -- > Erwan de FERRIERES > www.nereide.biz
