Overview¶

Squish contains several timeout settings that apply to starting and running the application:

Maximum Startup Time (s):

• Specifies how many seconds Squish should wait for a reply from the AUT (Application Under Test) directly after starting it (and before hooking up the AUT has succeeded).

• Applies before having successfully hooked up the AUT.

• Once this timeout has been reached while starting up the AUT it typically results in a log entry such as "RuntimeError: startApplication() failed" in the Test Results view.

• Default: 20 (seconds)

Maximum Response Time (s):

• Specifies how many seconds Squish should wait for a reply from the hooked up AUT before raising a timeout error.

• Applies after having successfully hooked up the AUT.)

• Once this timeout has been reached while starting up the AUT it typically results in a log entries such as "Fatal AUT stopped responding", "Detail: The AUT '' did not respond to network communication. Maybe it's stuck in an endless loop?" in the Test Results view.

• Default: 300 (seconds)

Maximum Post-mortem Wait Time (ms):

• Specifies how many milliseconds Squish should wait after the first AUT process has exited.

• Applies to AUTs that actually start the "real" AUT as a new/separate (sub-)process, like Java Web Start, but also third party Java application launchers. In those cases the first AUT process may exit before the second (the "real") AUT process has been hooked up by Squish. And this will cause Squish to abort its attempt to start (and hook up) the AUT with an error - unless hooking of the second AUT process succeeds within the number of milliseconds specified by this setting.

• Default: 1500 (milliseconds)

Configuring timeouts from the IDE¶

If your application normally requires at least 60 seconds to start up you need to inform Squish so that it will wait long enough. Select Edit > Server Settings > Application Behavior. The Server Settings window appears with Application Behavior selected.

Update the Maximum Startup Time (s) setting to the duration your AUT typically requires, plus approximately an extra 30 seconds to allow for temporary additional demand on the computer. For example, for an AUT that typically requires 60 seconds to start up "90" (seconds) should be specified.

Configuring timeouts from the command line¶

Alternately, you can configure the timeout duration from the command line via squishrunner.

To set the Maximum Startup Time to 60 seconds (default: 20 (seconds):

squishrunner --config setAUTTimeout 60

To set the Maximum Response Time to 600 seconds (default: 300 (seconds)):

squishrunner --config setResponseTimeout 600

To set the Maximum Post-mortem Time to 2000 milliseconds (default: 1500 (milliseconds)):

squishrunner --config setAUTPostMortemTimeout 2000

Also see Configuring squishrunner .

Related Information¶

• Finding the process that a window belongs to

• getting-started