View source | Discuss this page | Page history | Printable version   

Retail:Developers Guide/Retail/Automation architecture


The basics

The automation architecture was created focused on easy test creation and maintenance

Test creation


Automation engine

The automation engine picks up all the tests, then sort them, then executes the tests. When a test is executed, the

Project hierarchy

 +-- common
 +-- retail
      +-- pack
      +-- extmodules
      +-- stress

This is the basic project hierarchy. The common package holds support classes that overhaul the automation logic. The retail package contains the suites and tests. Inside the retail package, suites and tests are separated based on goal; e.g: the pack package verifies the Openbravo Retail Pack, the extmodules package verifies several modules added to the Retail Pack and the stress package verifies the Retail Pack under heavy load.

Execution flow

Retail automation execution flow.png

How to create a new project

A project in Retail automation contains the logic required for a complete set of test to be run in a server. For example, the Retail Pack is tested in several servers that run the contents in the package

To create a new project:


Note: an example can be shown in pi-mobile, rev 5362, changeset 0cb2bd0e751f, description 'Added a new custom project for BUT'

Retrieved from ""

This page has been accessed 1,916 times. This page was last modified on 10 June 2016, at 15:43. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.