Module Integrity test

Contents 1 Setup 1.1 Initial Setup 1.2 Continuous Setup 2 Process 3 javascript check 4 model check 5 java-api check

Setup

• Job specific to Module Integrity

Initial Setup

• hg clone https://code.openbravo.com/erp/devel/pi/ workspace
• install.source
• cd workspace
• hg clone https://code.openbravo.com/erp/devel/api-checks/ api-check

Continuous Setup

• Update workspace
• Install.source
• cd workspace/api-check
• hg pull -u

Process

The tests consist of 3 different groups:

• javascript api check
• model (pl,database,...) check
• java api check

javascript check

• ant run.javascript.tests -Dapi.details.path=<js reference folder>

The parameter must point to the js subfolder of the api-checks repository. The task will fail if it finds a violation and display details about it.

model check

• ant run.api.test.model -DstableDBdir=<model-reference-folder>

The parameter needs to point to the model folder in the api-checks clone.

java-api check

This check is done in two parts:

• ant -f <api-checks-clone>/java/tools/japitools.xml export.api -Dopenbravo.base=<path to current> -Djapifile=<daily>
• <api-checks-clone>/java/tools/japicompat -q <api-checks-clone>/java/reference/250.japi.gz <current>

The two parameters are the path to the japi.gz files of the repective builds.