3.25.3. Parameters for the test executor
Prev | 3.25. Using the test executor for testing from the command line | Next

### 3.25.3. Parameters for the test executor

- Once you have browsed to the correct directory and entered testexec.exe, you can enter the parameters for the test execution.

- The test executor has various parameters (Table 3.2, “testexec parameters”):

Detail | Parameter
--- | ---
Help | -h Gives parameter help
Project name | -project <project name> e.g. -project "ExampleProject"

Project version

-version <project version>
e.g. -version "1.0.0_release"
, -version "1.0" or -version "release".
If your version number consists only of a qualifier, then you enter the qualifier without the preceding underscore (e.g. -version "release"). If you are using a qualifier-only version number that begins with a number or contains an underscore, then you must use the preceding underscore (e.g. -version "_3" or -version "_Test_1").

Configuration file | -c <path to configuration file> e.g. -c "<pathToQADocs>/config.xml" Use this instead of entering arguments via the command line (Section 3.25.5, “Using a configuration file”)
Database URL (optional) | -dburl <URL> e.g. -dburl "db.example.de" If you enter this, you do not need to enter the -data or -dbscheme parameter (Section 3.25.3.3, “Using the dburl instead of workspace and dbscheme” ) You can find the dburl in the database preferences If no URL is given, the default will be used.
Database username | -dbuser <username> e.g. -dbuser "username"
Database password | -dbpw <password> e.g. -dbpw "password"
Server (optional) | -server <AUT Agent hostname> e.g. -server "localhost" This is optional if you want to use the embedded AUT Agent (Section 3.25.3.1, “Using a separate AUT Agent or the embedded AUT Agent”).

Port number (optional)

-port <port number>
e.g. -port "60000"
This is optional if you are using the embedded AUT Agent and want to use a dynamically chosen port. If you are using the embedded AUT Agent and want to specify the port then you should still enter a port number. If you are working with a separately started AUT Agent, this argument is required (Section 3.25.3.1, “Using a separate AUT Agent or the embedded AUT Agent”).

Test Suite | -testsuite <testsuite name> e.g. -testsuite "suite1" Use to start a Test Suite (Section 3.25.3.2, “Test Suites and Test Jobs”) Only one Test Suite or Test Job can be started
Test Job | -testjob <testjob name> e.g. -testjob "job1" Use to start a Test Job (Section 3.25.3.2, “Test Suites and Test Jobs”). Only one Test Suite or Test Job can be started.
AUT configuration name | -autconfig <configuration name> e.g. -autconfig "localconfiguration" Use when starting an AUT via a configuration (Section 3.25.3.2, “Test Suites and Test Jobs”).
AUT ID | -autid <ID> e.g. -autid "SimpleAdder1" Use when AUT was started via autrun (Section 3.25.3.2, “Test Suites and Test Jobs”).
Data directory (optional) | -datadir <path to external test data directory> e.g. -datadir "<pathToQADocs>/data" Use when you have test data for the test. e.g. from Excel. You can use relative paths (relative to the platform working directory).
Result directory (optional) | -resultdir <path to directory> e.g. -resultdir "<pathToQADocs>/results" Use when you want HTML and XML test result reports to be produced by the testexec. Test results will still be written to the database. You can use relative paths (relative to the platform working directory).

Result file name (optional)

-resultname <filename>
e.g. -resultname "PRODUCTIVE_TEST"
Use this to specify a name for the HTML and XML test result reports that testexec writes (if you have configured this).
If you do not use this parameter, a default name will be used that consists of the Test Suite name. Do not write a file extension - they are added automatically. If a file with the same name exists, it will be overwritten. If you use this option with a Test Job you will therefore only see the last result. You cannot write file names containing path information.

Generate Monitoring reports (optional) | -generate_monitoring_report Use when you want monitoring reports to be produced by the testexec. Reports will be written to the result directory.
No run option (optional) | -n e.g. -n Performs various pre-execution checks. There is a set of parameters to configure the no run (Section 3.25.6, “Working with the no-run option”).
Quiet option (optional) | -q e.g. -q Does not give out test information.
Timeout (optional) | -timeout <timeout in seconds> e.g. -timeout "3600" Enter an optional timeout for testexec.
No screenshot (optional) | -s no screenshots will be taken on errors.
No screenshots in HTML and XML (optional) | -sx screenshots will be taken on errors and written to the database but they will not appear in the XML and HTML reports created if you have specified a resultdir.
Maximum iteration count (optional) | -itermax <number of iterations> e.g. -itermax 50 Sets the maximum number of iterations for loops, used to avoid possibly infinite runs. The default value is 100.
Workspace | -data <path to workspace> e.g. -data "<pathToQADocs>/workspace" The ITE workspace with the preference settings for the database connection This is optional if you enter the -dburl parameter (Section 3.25.3.3, “Using the dburl instead of workspace and dbscheme”)
Database scheme | -dbscheme <scheme> e.g. -dbscheme "embedded" This is optional if you enter the -dburl parameter (Section 3.25.3.3, “Using the dburl instead of workspace and dbscheme”)

Table 3.2. testexec parameters

#### 3.25.3.1. Using a separate AUT Agent or the embedded AUT Agent

- When using testexec, you have the choice between working with an AUT Agent that you start separately, or using an embedded AUT Agent that is started automatically by testexec.

- If you want to use a separately started AUT Agent, then the AUT Agent must be started on the machine you are testing on. Enter the parameters for the server and port number to connect to this AUT Agent.

  | If you are working with Test Jobs, you must use a separately started AUT Agent, because you will require the AUT Agent to start the AUT via autrun.

- If you want to have testexec start and connect to an embedded AUT Agent automatically, then you have two options:

  - You can leave out both the parameters for the server and the port number. This will result in an embedded AUT Agent being started on a dynamically chosen port.

  - You can leave out the server parameter, but still enter a port number. This will result in an embedded AUT Agent being started on the port you define.

#### 3.25.3.2. Test Suites and Test Jobs

- You can either enter a Test Suite to be executed or a Test Job. Only one of these two commands is accepted for the test executor.

- If you are starting a Test Suite, your AUT will be started from its configuration. You must enter the configuration name using the correct parameter for the testexec.

- If you are starting a Test Job, testexec will start the first AUT required if you configure testexec to use an AUT configuration. If you configure testexec to use autrun, then you must make sure that the first AUT you require is already started with the autrun command. You must then enter the AUT ID as a parameter for the testexec. Any other AUTs required during the test must be started by autrun separately, or started as a part of the test itself. When working with Test Jobs that use autrun applications only, you must use a separately started AUT Agent, and not the embedded agent.

#### 3.25.3.3. Using the dburl instead of workspace and dbscheme

You can use the dburl parameter to specify which database should be used instead of entering the dbscheme and workspace parameters. This has the advantage that you do not need to create a workspace on the test machine that is configured for the correct database.

#### 3.25.3.4. Starting the test execution via testexec

1. Once you have entered all the necessary parameters, press »ENTER«.

2. The client will connect to the AUT Agent(either the defined separate AUT Agent or it will start an embedded AUT Agent then connect to it), connect to the database, open the Project, start the AUT (for a Test Suite) or connect to it (for Test Jobs) and then execute the Test Suite or Test Job you specified.

3. Once the test has finished, the client will show an exit code.

   - ”Exit code: 0” indicates that the test was successful.

   - ”Exit code: 1” indicates that the test contained an error.

   | To stop the test execution, use »CTRL+C«

#### 3.25.3.5. Passing on arguments to the JVM

The test executor also accepts arguments to pass on to the Java Virtual Machine. This means that you can, for example, increase the initial and maximum amount of system memory allocated to the JVM with the parameters -Xms<memory_size> and -Xmx<memory_size>, respectively. For example, the parameter -Xmx128M would make a maximum of 128 MB of system memory available to the test executor. When entering the standard parameters for the test executor, you may add -J<JVM_parameter> for each JVM parameter you wish to set. For example, -J-Xmx128M. Multiple parameters, like standard parameters, are separated by spaces.

Here is an example of defining mutliple JVM parameters:
-J-Xmx128M -JXms128M.