View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

ERP 2.50:Automated Testing/Branches and code promotion

Every new version of the ERP will make some tests fail, due to fixes and modifications done on the application.

Automated testing repository is synchronized with development, so tests can be executed on current stable application, on the nightly build and on the previously published version.

Currently, there are three stable automation branches and many more for updating old tests to new application fixes, developing new tests, and developing new automation features.

The basic code promotion flow is as follows:

  1. Automation development is made on a automation/pi-* branch.
  2. When the pi-* branch is stable, code is promoted to automation/int branch. The most common criteria of stabilization is three successful executions in a row, but it varies between projects.
  3. When the code is promoted to automation/int branch, an automatic execution of the suites will be launched.
  4. On a successful execution of automation/int jobs, code will be automatically promoted to automation/pi.
  5. On a successful execution of automation/pi, code will be automatically promoted to automation/main. Sometimes the erp/devel/main branch will be frozen to prepare a new Maintenance Pack; in this case the automation/main branch will be frozen too and changes will be sent to Release Management as transplant requests.

Contents

Branches for automation development

automation/pi-smoke: This branch is used to develop and maintain the smoke test suite. Bug fixes, changes to synchronize with the most recent erp/devel/pi branch and improvements on the code occur here.

automation/pi-regression: This branch is used to develop and maintain the regression test suite. Bug fixes, changes to synchronize with the most recent erp/devel/pi branch and improvements on the code occur here.

automation/pi-dbunit: This branch is used to develop and maintain the GUIUnit test suite. Bug fixes, changes to synchronize with the most recent erp/devel/pi branch and improvements on the code occur here.

automation/pi-ci: This branch is used to develop and maintain the Continuous Integration test suite. Bug fixes, changes to synchronize with the most recent erp/devel/pi branch and improvements on the code occur here.

automation/pi-idl: This branch is used to develop and maintain the tests on Initial Data Load module. Bug fixes, changes to synchronize with the most recent erp/pmods/org.openbravo.idl/ branch and improvements on the code occur here.

automation/pi-selector: This branch is used to develop and maintain the tests on Selector module. Bug fixes, changes to synchronize with the most recent erp/mods/org.openbravo.examples.userinterface.selector/ branch and improvements on the code occur here.

automation/splp: This branch is used to develop and maintain the tests on Spanish Localization Pack. Bug fixes, changes to synchronize with the most recent developments on splp and improvements on the code occur here.

Integration branch

automation/int: This branch is used to integrate all changes on previous development automation branches.

Stable automation Branches for testing current Openbravo developments

automation/pi: This branch is synchronized with the Openbravo ERP erp/devel/pi branch.

automation/main: This branch is synchronized with the Openbravo ERP erp/devel/main branch.

Stable Branches for testing previously Openbravo published versions

automation/2.40: This branch is synchronized with the Openbravo ERp erp/stable/2.40 branch.

automation/2.3x: This branch is synchronized with Openbravo ERp erp/stable/2.3x branch.

Retrieved from "http://wiki.openbravo.com/wiki/ERP_2.50:Automated_Testing/Branches_and_code_promotion"

This page has been accessed 2,931 times. This page was last modified on 3 April 2012, at 10:59. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.