OpentestBEEs

From AragoWiki

Revision as of 23:28, 3 August 2011 by Denix (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Back to Opentest's Home

Contents

Overview

BEEs, Build Execution Engines, belongs to the Service Providers layer of the Opentest architecture. Their task is to provide the software assets to the Test Execution Engines TEEs. Providing such software assets may involved either building them from sources or retrieving them from a given location.

Available BEEs

Each Build Execution Engines (BEE) is implemented as a STAF service, currently running these services require java version 1.6.x or later.

The following BEEs are currently available:

  • Arago: Build Execution Engine to build software assets for projects available at arago-project
  • File: Build Execution Engine to retrieve pre-built files. The file path is a UNC path and must be accessible from the machine where the File service is running.
  • Http: Build Execution Engine to retrieve pre-built files. The file path is a http url specified as http://server/filePath.
  • Ftp: Build Execution Engine to retrieve pre-built files. The file path is a ftp url specified as ftp://user:password@server/filePath.

Installation

The files that implement these execution engine services can be downloaded from http://arago-project.org/files/releases/opentest/0.0.19/. The installation typically follows a two-step process. First, the required files must be downloaded to the PC where the execution engine is going to run and second, the execution engine must register itself w/ the local STAF process (StafProc) running in the PC where the execution engine is going to run. After downloading the appropriate jar file, the execution engine(s) can be configured following the steps in the Generic Instructions to Register a BEE

Generic Instructions to Register a BEE

Register the BEEs with staf and the TMC, this can be done manually from a command prompt or during STAF startup by adding the following entries to the STAF.cfg configuration file in the BEEs computer.

  1. Grant access to all the computers in the framework with the following command trust machine ssl*://<subnet ip address> level 5 , i.e trust machine ssl*://192.168.*.* level 5, to allow files transfers between the dispatcher and the other computers in the framework without problems.
  2. Set the following staf shared environment variable using staf’s var service: staf/tmc/machine is used by the BEE to resolve the name or IP address of the TMC machine so that it can register with it.
  3. Register the BEE with staf and the TMC with the following command: SERVICE <bee name>@<id> LIBRARY JSTAF EXECUTE <bee service jar file> [PARMS <registration params if any>]. For example:
  • For FILE BEEs (run only on windows) SERVICE file@1 LIBRARY JSTAF EXECUTE C:/TestAutomation/FileBee.jar
  • For FTB BEEs: staf local SERVICE add SERVICE ftp@1 library JSTAF execute /home/a0850405local/code/automation/tmp/FtpBee.jar
  • For HTTP BEEs: staf local SERVICE add SERVICE http@1 library JSTAF execute /home/a0850405local/code/automation/tmp/HttpBee.jar PARMS "proxyhost=<your http proxy> proxyport=80"

Developing new BEEs

  • Opentest allows and encourages people to develop their own BEEs if there isn't an existing BEE that suit their needs.

As mentioned before all the Opentest components are implemented as STAF services, so to implement a new BEE it is required to implement a new STAF service that complies with the following BEE Interface

  • A sample BEE implementation can be found at [1]
  • For a more detailed explanation about how BEEs fit into the overall system, please read [2]
Personal tools