From AragoWiki

Revision as of 18:36, 13 September 2013 by Chernandez (Talk | contribs)
Jump to: navigation, search


How-To Install Opentest Client tools

  • Find a Ubuntu system (10.04 or later should be fine)
  • Download and untar latest opentest_installer*.tar.gz (recommended 13.09 or later) from
  • Run the installer (e.g. ./ and select option 8 (Command Line Tools). This option will also install the STAF utility. For installation details see the list below:
    • The installer will install Java if required
    • Then it will install STAF (you can leave all the default install values)
    • Then it will install opentest_client components. You can leave default values for most options, however subnets must be entered. If you are in the US we recommend entering at least following 3 subnets (separated by spaces): 158.218.*.* 10.218.*.* 128.247.*.*
    • When prompted for the Tools installation menu select option 1 to Install All tools.
    • When prompted where to install the files you can enter . to install in the current directory. You should see this directory in the next prompt.
  • Finally you can select option 9 to quit.

How-To Start STAF

  • Check if STAF is running
$ staf local help
Usage: STAF [-verbose] <Endpoint | LOCAL> <Service> <Request>
  • If you don't get an error while running staf local help command, then STAF is running and you are good to go. However if you do get an error then you need to open /usr/local/staf/ and verify that STAF_INSTANCE_NAME is set to a value as shown below
if [ $# = 0 ]
   if [ $1 != "start" ]
       # Ignore "start" STAF instance name
  • Source the /usr/local/staf/ script to properly initialize your environment for STAF (assuming that STAF was installed in the default location).
    . /usr/local/staf/
  • Finally run /usr/local/staf/ to start STAF. Cat nohup.out file to check correct initialization
$ ./ 
$ nohup: appending output to `/home/charliebrown/nohup.out'
$ cat /home/charliebrown/nohup.out
Machine          : charliebrown
Machine nickname : charliebrown
Startup time     : 20130905-18:06:02
  • You should now be able to run the staf local help command and verify your STAF installation.

How-To Run your own tests on the boards Farm

 # Simple test to boot and echo 'hello world' upon booting.
./ -s "echo 'hello world'" <options>

The command above will not run by default without some options being passed. At a minimum you should specify the board farm to use, but likely you will also add your kernel image to test

How-To Run ltp-ddt tests on the boards Farm

./ -t <LTP-DDT testplan name> <options>

The command above will not run by default without some options being passed. At a minimum you should specify the board farm to use, but likely you will also add your kernel image to test

How-To Run Testlink tests plans on the boards Farm

./ -T <Testlink testplan> <options>

The command above will not run by default without some options being passed. At a minimum you should specify the board farm to use, but likely you will also add your kernel image to test arguments help

command help

# use -h flag to show command help
./ -h

-hw argument

The -hw argument selects the type of hardware (aka DUT) to run the tests on. It is also possible to specify capabilities or requirements that selected DUT must have. For instance, capabilities could be used to ask for a board that has an usb mass storage device attached to it. The argument syntax is -hw evm,capabilities where capabilities is an optional underscore-separated list of strings Valid evm names are the same used by OE/Yocto: am335x-evm, omap5-evm, beaglebone, dra7xx-evm, etc. For valid capabilities see Capabilities cheat sheet ... -hw omap5-evm,linux

-p, -b, -k, -m, -d, -r, -n Software arguments

Set software images (i.e. bootloader, kernel, filesystem, etc.) to used for the test. It is not mandatory to provide all of them. For example if bootloader (-p and -b) are not provided then the system will try to boot the DUT using whatever bootloader image is already installed on it. Most software image values can take either a local path or a http/ftp url. Use ./ -h for more details

-u, --user-bins argument

Executable or tarball of executables that should be installed on FS. This is useful for cases where user wants to run a binary that is not available in the default filesystem The value provided can be either a local file or a public http/ftp url ... -u /home/tmp/myapp

-s, --script argument

Use this option to run any arbitrary commands or a shell script in the DUT. The syntax is either a string of semicolon-separated commands (e.g. "echo 'hello'; echo 'bye'") or a path to a shell script. In either case the test will pass if the return value of the commands or script is zero. ... -s /home/tmp/

-t, --tests argument

Use this option to run your own ltp-ddt test plan. Please note that -s, -t and -T are mutually exclusive options ... -t mytests

To create your own ltp-ddt test plan follow this steps:

  • Update default tests. This will clone ltp-ddt project if required.
./ -U
  • Create a copy of default test plan
cp tests/ tests/
  • Modify tests_to_run list in tests/ to suit your needs by copying entries from tests_available list into it.

Each entry in tests_available lists points to a ltp-ddt test scenario (aka test suite). The syntax is:
<test scenario name>:<setup requirements>:<test cases filter>

-T, --testplan argument

  • Use this option to run a Testlink test plan. If you use this option results will be stored in the Testlink server.

The Testlink Testplan name syntax is: <project name>:<testplan name>. For example:

./ -T linux_psp2:ch_sandbox
  • To get the list of available projects, use following command:
./ --list-projects
  • To get the list of available testplans on a project, use --list-testplans <project ID> where project ID can be obtained from --list-projects command. For example:
./ --list-testplans 1140921

The above command will return the list of testplans for LCPD linux. linux_psp2 is the project name that host LCPD's linux test plans.

Please note that --list-testplans uses project ID, while -T uses project and testplans names.

-f, --farm argument

forces usage of a board in a farm.

-f tigt_farm
-f tid_farm


advanced-params are variables that advanced users can set to tweak execution. At the moment the only advanced-params supported by is var_use_default_env. Usually will try to boot the DUT using provided software images (i.e. kernel, filesystem, etc.), but advanced users may change that default behavior.

  • var_use_default_env=1 means Boot using default environment (i.e. env default -a -f; boot )
  • var_use_default_env=2 means Do not touch uboot env, just power cycle and let it go


  • If you get ImportError: No module named argparse while running then you need to install python-argparse
$ sudo apt-get install python-argparse
Personal tools