It is also possible to perform a headless running of Validator tests using a pre-configured simulation target and the names of tests. After creating the tests in Designer and creating a simulation launch, local or remote, a user can run a test or a group of tests from the command line or scripting environment.
All of the Storyboard executables will be located in:
PATH_TO_INSTALL/Storyboard_Designer/storyboard
directories, though on each desktop platform they are named slightly differently
Windows:
..../Storyboard.exe -application com.crank.validator.ui.validatortestrunner model=<PathToGDEFile> tests_to_run="test_name[:test_name_2:test_name_3:...]" config_name=<ConfigurationName>
Mac:
..../Storyboard.app/Contents/MacOS/Storyboard -application com.crank.validator.ui.validatortestrunner model=<PathToGDEFile> tests_to_run="test_name[:test_name_2:test_name_3:...]" config_name=<ConfigurationName>
Linux:
..../Storyboard -application com.crank.validator.ui.validatortestrunner model=<PathToGDEFile> tests_to_run="test_name[:test_name_2:test_name_3:...]" config_name=<ConfigurationName>
Note: Storyboard requires a display, so to run in a true headless environment a Virtual frame buffer needs to be setup.
Xvfb :1 -ac -screen 0 1024x768x8 export DISPLAY=:1 ..../storyboard -application com.crank.validator.ui.validatortestrunner model=<PathToGDEFile> tests_to_run="test_name[:test_name_2:test_name_3:...]" config_name=<ConfigurationName>
Where the model is the full path to the Storyboard Designer model file. This model file will be used to search for tests to run. The tests_to_run option specifies the tests that need to be run. The config_name parameter specifies the name of the launch configuration to run. This needs to be provided so that Validator knows whether or not to run the tests locally or remotely.
Additional Options
The -data option Is used to specify the workspace to be used when performing the export. This workspace should not be opened by other instances of Storyboard. This is helpful for Storyboard to find your launch configurations in your project.
It is specified as follows:
..../Storyboard.exe -application com.crank.validator.ui.validatortestrunner -data <PathToWorkspace> model=<PathToGDEFile> tests_to_run="test_name[:test_name_2:test_name_3:...]" config_name=<ConfigurationName>
The -consoleLog option is used to enable additional logging to the console. The -noExit option is used to prevent the application from closing automatically after performing the export. This is sometimes useful to keep the log console open post-mortem.