It is possible to start Wetator with

• a dedicated configuration file
• a dedicated variable definition file
• one ore many test definition files; as long as you provide not absolute path it is also possible to use '*' as wildcard
• a flag to force appending of the current results to already existing ones

Additionally you can provide the '-log' parameter to get a really detailed log output of all things Wetator does. This option is mainly for debugging and support.

Examples:

wetator -p my.properties
Starts Wetator with the configuration 'my.properties'

wetator -p my.properties -var variables.properties
Starts Wetator with the configuration 'my.properties'. Additional variable definitions are taken fon the file variables.properties (varialbes defined inside variables.properties are overwriting the ones from my.properties). Use this e.g. to have separate password variable not checked in but available as (protected) file on the ci server.

wetator test1.wet
Starts Wetator and directly executes test1.wet (no file selection dialog).

wetator test1.wet test2.wet
Starts Wetator and directly executes test1.wet and test2.wet.

wetator *.wett
Starts Wetator and directly executes all files with the extension 'wett'.

wetator -p my.properties test1.wet test2.wet
Starts Wetator with the configuration 'my.properties'. Wetator directly executes test1.wet and test2.wet.

wetator -append test4.wet
Starts Wetator and append the results of test4.wet to the already existing ones
. Append requires to have the option 'wetator.distinctOutput' set to false. Additionally the configuration used for this call should be the same as for the ones before (because only the config of the first test will be shown in the report).