Next: Directory Layout, Previous: Execution sequence, Up: The ARTE Core
You can get a whole list of arguments to be passed to the arte command
calling it with the -h option:
$> arte -h
Usage: arte [options]
Options:
-h Show this help
-v Verbose mode, showing all possible logs
-s Silent mode, showing only the errors
-l Create a log of all tests in HTML format
-m Avoid deleting the temporary directories in /tmp
-t Disable the timeout failure of tests
-c FILE Specify the path to the ARTE configuration file
-d INTEGER Specify the timeout for each test, in seconds
-f Avoid forking for each test
-r RTAFILE Only execute the specified RTA. It must be in the
'tests' directory of the suite.
-x RTAFILE Decompress in the suite Sandbox the specified RTA
-k Create an RTA from the Sandbox, check and execute
|
The default timeout for each test is 15 seconds, and if more time is needed,
the -d INTEGER argument should be used. With this option, the default
timeout for all tests is changed in the current ARTE execution.
With the -x RTAFILE argument, the RTA file given in ‘RTAFILE’
is decompressed (which must be in the ‘tests’ directory of the suite) in a
new directory called ‘sandbox’ (under the suite directory). In addition to
just decompressing the RTA file, it creates a .rtaname file in the same
directory, containing the name of the original RTA file. The contents in the
‘sandbox’ can then be modified, including the filename stored in the
.rtaname file to rename the RTA file that can be then created with the
-k argument. This newly created RTA is stored in the ‘tests’
directory of the suite, and directly executed.
An standard execution of ARTE could just be:
$> arte -v -l
|