This documents the way Jenkins Continuous Integration Build Server is set up to give a comprehensive Quality Assurance environment for the ADempiere361/iDempiere project. You can see a live demo at http://berliserv.net:8080/
Sequence of testing:
1. adempiere361
2. Database
3. Silentsetup
4. Server2
5. WebUITesting
The above has projects set up for the pulling of any code change from the trunk repository, then build it, apply the database seed and migration scripts since last release, and then run Fitnesse business logic tests for the Java client, then run the application server, and run the Selenium testing of the ZK Web interface. Lastly you can test the RUN_Server2Stop of the Apps Server.
Above is the Selenium testing that opens the Webstore, check a product category, login into the ZK UI, search for the Sales Order item, launch it, create a new Std Order, assign a Business Partner and Warehouse, creates two orderlines of different products and qtys, toggle the gridviews, then return to the main tab and confirm the order.
There is Selenium grid to use but there are sometimes conflicts within the Debian server that hosts these and you may have to setup the following:
1. Firefox profile from headless Firefox in the Debian server
2. An init.d script for Selenium to run in the background
3. Jboss of ADempiere set to another port as it conflicts with port 4444 of Selenium
In next post will be the init.d script, Jenkins build and bash shell scripts. All work is committed to http://adempiere.svn.sourceforge.net/vi ... eleniumHS/
Main persons to thank are banym Dominik Zajac of BayCIX / D2C2 of Munich, Germany,
didiber Dietmar Berlinger of PROMANDANT AUSTRIA.
THIS CONTRIBUTION IS SPONSORED BY SYSNOVA (Thanks to ZeeShan).