Seleniet has grown from a small command line utility for local selenium based testing into a full blown web and shell test automation tool with integration to external test case management tools and detailed test result reporting. With this extension comes a plethora of command lin eswitches that can be used to tailor the execution.
You can either supply these parameters directly via command line or save thme in a *.selexprof file and run seleniet specifying the profile file to read the params from:
seleniet.bat run --profile XXXX.selexprof
The following parameters are available:
mandatory parameters are marked with one asterisk “*”, parameter sets where one of a group of is mandatory are marked with two asterisks “**”
For web based tests one of the two following parameters need to be supplied:
–browser [firefox|chrome|ie|marionette|android] **
Starts the specified browser. marionette and android are experimental features and are not recommended for productive use
The firefox specific parameters –ffprofile or –ffprofdir allow to specify which firefox profile should be used by the to be started firefox browser.
–grid gridfile gridhub **
Starts an browser instance specified via grid properties on the gridhub server
example gridhub: http://gridserver:4444
Specifies the position and size of the browser window (in pixels)
–screenon / screenoff
Flag whether to save a screenshot after each step or not, default is –screenoff
Number of seconds to wait for web / DOM elements to appear before throwing a timeout error, defaults to 20 seconds
–url http(s)://starturl.test *
URL of the application under test / URL opened at the start of the test run
External system / test case parameters
–zephyr projectname cyclename **
Reads test case definitions from external Jira/Zephyr system for given cycle of given project
–folder filefolder **
Reads test case definitions from the local file system starting from the given folder
–trac catalog testplan **
Reads test case definitions from external TRAC system (TestMgr plugin) for given catalog and test plan
–xls excelfile ** DEPRECATED
Reads test case definitions from an Ecel sheet (XLS 2007), DEPRECATED
–testlink xmlexportfile cfgfile ** DEPRECATED
Reads test case definitions from an TestLink server, DEPRECATED
Specifies where to read the obj repo from. Can be XLS or CSV file /url. Defaults to “ObjRepository.xls”
Flag whether the test results shall be updated to the external system (if applicable) or not
Name/key of the test case to perform. If supplied only THIS test case (and all of its sub tests) will be performed.
Name of the folder to store test results and artefacts to. Defaults to “tests”
Flag whether to start interactive gui mode. Failures will be reported by a popup and need to be clicked to continue test execution. This allows to analyse test failures in more detail.
Flag whether to start non interactive console batch mode.
Flag whether to create a local test report based on JUnit report template in local test dir folder
Number of seconds the test run must not exceed. After this timeout the test execution will be aborted as soon as possible.
Deprecated flag whether to pause on test failures. Now subsumed in the –gui flag
Screenrecording parameters (experimental)
Flag whether to record browser window or not
Number of frames per second (minimo 3, up to 20 depending on your hardware)
Area to record
Name of the file to store the screen recording to
To store command line parameters into a selexprof file each of the parameters and each of its arguments need to be written to a new line.
shall be written to the file as