Is Opentest right for me?
If you are working with one of the TI products that use Opentest then you might want to consider using Opentest for your own testing. Depending on your situation, you might want to use parts of Opentest like a Test Execution Engine instead of the full system. The full system is tailored to handle situations where there are many users working on many projects in parallel. If your team is small and you are only working on one project then it might make more sense for you to use some components of Opentest rather than the whole solution.
How does testlink and staf tie in together? I do not see configuration options in either that describe the interface (system level tie in)
There is a “Execute & Save” button in the TestLink Execute tab that triggers a Staf call from TestLink to the Test Master Controller. Every single machine that it is part of the test automation system MUST be running Staf. The machines in the system communicate w/ each other by calling Staf request on each other. TestLink only talks to the Test Master Controller (Dispatcher service). The Dispatcher will then contact the appropriate Build and Test Execution Engines. Once the TEE completes a test, the test results are sent to the Dispatcher and then the Dispatcher writes them to the TestLink database
What is the format for importing test result into TestLink
What is the format for importing test suite(s)
The preferred way to import is using XML files. You can also import test cases to TestLink using XLS format; but the support is very limited. You can not import KEYWORD or CUSTOM FIELD. Check Sample test suite file
Why the exported XML is empty after I click Execute and Save Results button
Currently, we only export automated test case after you click this button. So check if 'execute type' is set to Automated. If it set to Manual, this test case will not be exported.
What is the format for importing requirements into TestLink
TestLink uses XML files to import requirements.
The xml schema defines following elements:
- Component: Typically used to group related requirements (i.e. for Linux validation possible values could be USB, Ethernet, I2C, etc.)
- Type: Functional, Performance, Compliance, Reliability (users can use any value but should be consistent)
- Platform: Pipe-separated ('|') list of platforms that requirement is applicable to.
- Release: The name of the release that requirement is applicable to.
- Implemented: Is the requirement implemented on this release? Boolean field to allow user to filter requirements reports.
Check Sample requirements file
How do I import and assign requirements to test cases in TestLink
In Testlink's home tab under the requirements section, there are two links:
- Requirements Specification Document: Allow user to create new requirement specification document and import requirements under it. It also provides requirements analysis option.
- Assign Requirements: Allow user to link test cases to requirements. There are drop-down boxes to filter requirements based on their component, type, etc.
How do I analyzed requirements coverage
Three types of analysis are possible:
- Home -> Requirements Specification Document -> Analyze button: It tells which requirements are covered/not-covered/not-testeable. This analysis is not specific to any test plan, instead it checks against all test cases defined.
- Results -> Requirements based report: It tells which requirements passed/failed/blocked/not-verified-yet for a given test plan.
- Results -> Test cases without Requirements Assignment: It tells which test cases in the given test plan does not have any requirement assigned to them.
I forgot my password, what should I do
In testlink login page, click 'Lost Password' link and then enter your login name. Testlink will reset password and send the new password to based upon your user name and the email address you entered when you setup user account. After you login with this new password, you can click Personal link on the top right corner and change the password to whatever you want.
What services are provided by the Test Master Controller
The test master controller layer is implemented as four separate staf services: the dispatcher, which is the front end of the test master controller to testlink, schedules jobs based on test session request coming from test link; the resource manager used by the dispatcher for resource reservation and allocation; the test link adapter used by the dispatcher to write results to the testlink database; and the email service used by the dispatcher to send email notifications to the user once a test session has finished execution.
What account should Staf run under? Does the windows account have to match the Linux account?
Typically it should not matter because in the Staf config files one can grant access to anybody on a given subnet (x.y.z.*). So any Staf machine can request services on another Staf machine as long as it is on the same subnet.
My system was setup with DynaLoader 1.05 and libPLSTAF.so is expecting 1.04. How do we get around this (assuming we cannot change the system version of perl?
If you are get libPLSTAF.so errors, you must likely will need to rebuild the libPLSTAF.so in your setup. The instructions for rebuilding it can be found at: http://staf.sourceforge.net/current/stafdg.html#Header_buildPerl
What are the available BEE types?
- File BEE: Use to retrieve pre-built files from Windows' UNC paths
- HTTP BEE: Use to retrieve pre-built files from HTTP servers
- FTP BEE: Use to retrieve pre-built files from FTP servers
- Arago BEE: Use to build files from existing Arago recipes.
What are the available TEE types?
- VATF TEE: Host-based or Target-based execution engine written in Ruby that is capable of running test on many different environments.
- STAX: Test execution engine provided by STAF.
How do I add a new test equipment driver in VATF
- First you need to write the ruby code that implements the driver in a new file inside the test_equipment folder. For Example: VATF/test_equipment/my_new_driver.rb
- Then you need to add a reference to the new driver in the file VATF/test_equipment/test_equipment.rb. For example:
require 'test_equipment/q_master' require 'test_equipment/q_master_dll' require 'test_equipment/spectra_lab_cli' require 'test_equipment/apc_power_controller' require 'test_equipment/video_clarity' require 'test_equipment/my_new_driver'
How do I set site-specific information in VATF
Some site-specific information like e-mail server address, log files repository, etc must be specified in the site_info.rb file located in the vatf's root directory.
How do I point to a specific ruby version
Before you call /usr/local/staf/startSTAFProc.sh to start STAF, set PATH, GEM_HOME and GEM_PATH environment variables at the beginning of the /usr/local/staf/STAFEnv.sh file. For example:
PATH=/usr/local/staf/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin:/home/bin GEM_HOME=/var/lib/gems/1.9.1 GEM_PATH=/var/lib/gems/1.9.1