OpenTest is composed of several open source projects, each of which require some manual setup and configuration. To facilitate the process of installing and configuring Opentest an opentest installer have been provided at Opentest Binaries that includes the latest version of each of the components where Opentest have been validated and known to work.
To run the installer untar the archive, open a shell, and execute the install_opentest.sh script located inside the opentest_installer folder.
During installation the user will be asked to enter information regarding the setup of the Opentest framework being installed; therefore, it is recommended to get familiar with the Opentest architecture before using the installer. After installation most of the main components of the framework will be installed and configured but the user will still have to modify some of the configurations files according to the setup where the framework will be used. Some of the question asked during installation are:
Each of the sub-components of Opentest has certain prerequisite programs. As the installer only supports apt based hosts, these are listed in apt-get'able form currently.
Installer: If you are behind a proxy you must have your environment configured to work behind a proxy prior to launching the installer.
All: All precompiled binaries are provided as 32bit programs so ia32-libs must be installed. Various parts of opentest will invoke sudo so you must have the user that is running STAF setup to invoke sudo without a password. At this time the list of commands required is not logged.
TEE: The TEE must have telnet (telnetd) and tftp (tftpd-hpa) servers installed. In addition, targets which support XMODEM/YMODEM loading will require the lrzsz package to be installed. You will also need to add a new user (that can login via password) for tms.
STAF: If talking to DUTs diretly via serial (rather than via a console server) the user running STAF must be part of the dialout group (assuming default udev rules).
Common answers to questions from the installer
Questions asked by many components
- Please enter staf installation folder [/usr/local/staf]:
Refers to the location where the STAF service was installed.
- Please enter the subnets where OpenTest will operate (use space for more than one subnet, ex. 10.218.*.* local 158.218.*.* *.ti.com) :
Refers to the subnets where the Opentest framework will operate. For example, if all the components are going to be installed in one host the answer can be "localhost" or "127.0.0.1". If some TEEs operate on 10.218.*.* subnet, the BEEs operate on the 158.218.*.* subnet and the TMC operates in the 1.2.*.* subnet than the answer will be "10.218.*.* 158.218.*.* 1.2.*.*"
- Where would you like to install Opentest files?
- Please enter the TMC machine IP address (ex: local, 111.222.333.444. TIGT typically uses 188.8.131.52, TII typically uses 172.24.128.156):
Refers to the IP address of the machine where the TMC components were installed.
- Enter the IP address of the interface used by Opentest:
Refers to IP address that will be used by Opentest where the current components are being installed. <br/.
STAF installation questions
STAF will ask what version of perl/python/tcl are found on the host, and if it should use the system one or not. Given how we utilize STAF, the answers are irrelevant.
Testlink installation questions
- Enter Testlink test request export directory :
Refers to a folder where all the Test session's xml data will be exported when a Test Session is started by clicking on the "Execute and Save Results" button in Testlink.
- Enter MySQL administrator username:
Installing testlink requires installing MySQL which included in XAMP. This question ask the user to enter the Username of the administrator for this MySQL db. Do not use root.
- Enter MySQL administrator password:
Refers to the Password that will be configured for the username provided in 2.
TMC installation questions
- Please enter Testlink's xml rpc URL (ex: http://localhost/testlink/lib/api/xmlrpc.php):
Refers to the XML RPC server included in testlink, the answer to this question if typically "http:<IP address or name of the Testlink server>/testlink/lib/api/xmlrpc.php"
- Please enter Testlink's default user development key (ex: 2721b84044654e0b9a8cac8235812345):
Refers to the default development KEY needed to write to Testlink's db. This devkey is obtained by login in Testlink; clicking on the "Personal" link located on the top right corner of the home page; going to the "API Interface" section of the Personal page and clicking on the "Generate a new key" button
- Please enter the mail server used for this site (ex: smtp.mail.ti.com):
Refers to the email server that will be used to send the Test Session completed email once a Test Session has finished execution.
TEE installation questions
- Enter TEE name (ex: vatf, dss) :
Refers to the name that will be given to the current TEE being configured.
- Enter TEE id (ex: 1, 2, android1, linux1):
Refers to the ID associated with the current TEE being configured.
- Enter TEE capabilities (semicolon separated list of hardware assets enclosed in square brackets [<asset>,<asset capability];[<.....;[<asset>, <asset capability], for example [am335x-evm,android_ics];[linux_server]):
Refers to the hardware assets associated with the current TEE being configured.
- Enter TEE test scripts folder :
Refers to the base folder where the execution scripts used by will be cloned.
- Enter TEE execution engine folder [/usr/local/vatf]:
Refers to the location where the executable or execution script of the execution engine associated with the current TEE being configured is located.
- Enter TEE xml result path:
Refers to the PATH where the current TEE being configured creates the XML containing the results of the Test executed. For example /usr/local/vatf/vatf@1_results.xml
- (Optional) Enter TEE description:
Optional Parameter the refers to a string describing the current TEE being configured.
VATF installation questions
- Please enter vatf install location [/usr/local/vatf]:
Refers to the location where the vatf sources will be cloned.
Installing and configuring Opentest can be a tricky process. Please see Opentest First Steps for a walkthrough of the install, configuration and "hello world" style test runs.
Currently the installer is only supported on apt based Linux based system.