licenseFile

Path to Q7 license file. Default value is ${user.home}/com.xored.q7.runner.l9, so it is possible just drop license file to C:\Documents and Settings\user on WinXP, C:\Users\user on Win7, /Users/user on Mac OS X or /home/user on Linux and do not care about this argument

"C:\licenses\q7runner.license"

No

aut

Platform-specific path to application under test

"C:\Downloads\eclipse"

Yes

import

Semicolon-separated list of project folders with Q7 tests or resources to link

"C:\work\q7project1;c:\work\q7project2", "C:\singleQ7Project"

Yes

autWsPrefix

File prefix for application-under-test's workspace. The workspace prefix given will be suffixed with incrementing restart index to make sure
no data is lost in case of application-under-test restart, hang or crash.

"C:\work\aut-workspace-"

Yes

junitReport

File path to save JUnit report with test exec results

"C:\work\q7results.xml"

No

htmlReport

File path to save HTML report with test exec results

"C:\work\q7results.html"

No

autConsolePrefix

File prefix for application-under-test process output. It will be appended with incrementing restart index for the same reason as -autWsPrefix arg.

C:\work\aut-console-output-

No

testOptions

Semicolon-separated list of Q7 Runtime options (see description below)

"testExecTimeout=600"

No

autArgs

List of arguments for application-under-test separated by semicolon.

-showsplash;org.eclipse.platform

No

autVMArgs

List of arguments for application-under-test's JVM separated by semicolon.

-Xmx1024m;-XX:MaxPermSize=512m

No

skipTags

autVM

Java VM to use with application-under-test. By default it is set to the same Java VM which is used for Q7 Runner launching

"C:\Program Files\Java\jre_1.6.0_25"

No

timeout

Overall execution timeout in seconds, default value is 18000 (5 hours)

3600

No

connectTimeout

application-under-test connection timeout in seconds, default value is 300 (5 mins). Very unlikely requires to be increased

7200

No

contextRunnableTimeout

180000

Context applying timeout.

contextsWaitforjobsTimeout

30000

If there are any jobs started after context applying, wait for their completion during this time (in milliseconds).

jobDebugjobTimeout

300000

Timeout in milliseconds for jobs scheduled from eclipse Debug plugin.

jobNulifyRescheduleMaxValue

50

If job reschedules itself more than times specified by this parameter, Q7 stops setting delay to 0 (see jobScheduleDelayedMaxtime parameter).

jobSleepingStepTime

200

When job is in sleeping mode (see jobTreatAsSleeingTimeout option), execute commands with given delay (in milliseconds) between commands.

jobSleepingStepTimeout

120000

Wait timeout in milliseconds for stepping jobs (see jobTreatAsSleepingTimeout and jobSleepingStepTime)

jobTreatAsSleepingTimeout

10000

If job executes more than this time (in milliseconds) and sleeps (i.e. executing Thread.sleep() or Object.wait()), then Q7 considers that this job is waiting for some user actions and continues to the next command.

q7ImageCapture

false

Whether to capture screenshot from AUT on every ECL command

timerExecsWaitNullify

100

If Display.timerExec is scheduled for the delay less than this value (in milliseconds), set delay to 0.

autStartupTimeout

300

How many seconds Q7 should wait for application startup.

jobHangTimeout

30000

Job hang skip timeout in milliseconds. If job is running longer than this time, Q7 Runtime considers that it is hung and moves to the next command.

jobSchelduleDelayedMaxtime

600

Max job scheduled delay to be waited for in milliseconds. If job is scheduled with delay less than this value, Q7 sets delay to 0 and waits for job completion (also see jobNullifyRescheduleMaxValue). Otherwise Q7 Runtime does not wait for job completion if it is scheduled with a delay greater than this value.

launchingKillAutOnConnectError

false

Kill AUT on connect error. Whether Q7 should kill application-under-test if it cannot connect to it.

eclExecutionDelay

0

Wait for a given milliseconds between each ECL command. This can be useful when things go wrong at some point and it is hard to determine when by looking at execution. Setting this value to, say, 500, allows to inspect Q7 actions in more details.

workspaceClearForceGc

true

Forces garbage collection on workspace cleanup.

diagramPartLocatorFeatureIdentityNames

id,title

Use following EMF features for part identity

diagramPartLocatorIdentity

ClassName

Non EMF object identity method

diagramPartLocatorNameFeatureSupport

true

EMF object identity by 'name feature' support

diagramPartLocatorTextSupport

true

Use text content for part identity