Skip to end of metadata
Go to start of metadata

Execution settings help users to set preferred behaviors for Katalon Studio during test execution. 

Default Execution Settings

You can configure general execution preferences by accessing from main menu: Project > Project Settings > Execution > Default.

Where:

Field

Description

Default execution

The default environment that Katalon Studio will use to execute automation test.

Default implicit timeout

The default timeout period (in seconds) that Katalon Studio will wait for the application under test to be loaded when executing automation test.

Post-Execution Options

These options decide the actions that Katalon Studio will perform after finishing automation test.

  • Notify me: Specify whether you want to send email notification.
  • Open report: Specify whether the report generated after your test suite finishes its execution will also be open immediately.
  • Terminate drivers: Specify whether any driver remains after execution will be terminated.

All the above preferences are saved into .prefs files under the “config\.metadata\.plugins\org.eclipse.core.runtime\.settings” location in your Katalon Studio build folder. You can manually modify the values in files to change these preference settings.

 

WebUI Settings

These settings decide the general behavior of Katalon Studio when executing WebUI testing. You can configure WebUI execution preferences by accessing from main menu: 

Window > Katalon Studio Preferences > Katalon > Execution > WebUI.

Where:

Preference Setting

Description

Delay between actions

The time for Katalon Studio to wait between test steps when executing test cases

Default wait when IE hangsSpecify the default period of waiting that Katalon Studio should use in case IE hangs
Default page load timeout
  • Wait until the page is loaded: Katalon Studio will wait for web page to load completely
  • Wait for (in seconds): The default timeout period (in seconds) that Katalon Studio will wait for Web page to load

All the above preferences are saved into .prefs files under the “config\.metadata\.plugins\org.eclipse.core.runtime\.settings” location in your Katalon Studio build folder. You can manually modify the values in files to change these preference settings.

 

Desired Capabilities 

You can modify extra Desired Capabilities when executing automation test in Katalon Studio. Here is the list of all execution modes that support modifying Desired Capabilities.

SettingsDescription

Project > Settings > Execution > Custom

Define a custom option for execution along with its Desired Capabilities.

 

Project > Settings > Execution > Default > WebUI > Chrome (Firefox, IE, Safari, Edge)

Define Desired Capabilities for local execution using Chrome, Firefox, IE, Safari or Edge.

 

Project > Settings > Execution > Default > WebUI > Remote Web

Define Desired Capabilities for execution on remote web server.

 

Project > Settings > Execution > Default > Mobile > Android (iOS is available in macOS)

Define Desired Capabilities for execution with Android and iOS devices.

 

Project > Settings > Execution > Default > WebUI > Headless

Define Desired Capabilities for execution with headless instance.

 

 

Adding a Desired Capability is similar across those settings (except for Custom execution). The step to add a property for execution are as following: 

  1. Click the Add button of command toolbar above the Desired Capabilities list.
  2. A new row will be added to the list.
  3. Provide the name of the property that you’d like to configure. Refer to https://github.com/SeleniumHQ/selenium/wiki/DesiredCapabilities to know which properties of each web browser are supported by Selenium. For desire capabilities to be used with Appium, refer to this list: http://appium.io/slate/en/master/?ruby#appium-server-capabilities.
  4. Specify the type for the property by clicking and expanding the dropdown under the Type column.
  5. Define value for the property. Refer to Value Types for details regarding how to input value for different types.

 

Desired Capabilities for Remote Web

In case of remote execution on Web Server, you need to provide details of the server when configuring Desired Capabilities.

Where:

  • Remote web server URL: provide the URL of the remote web server that will be used.
  • Remote web server type: Specify the type of the remote web server (i.e., specify which test automation framework is currently installed and used in the remote web server, whether it is Selenium or Appium).

Desired Capabilities for Mobile

In case of Mobile execution, you need to select the device when configuring Desired Capabilities.

Where:

  • Device Name: the device to apply Desired Capabilities settings on.

Desired Capabilities for Remote Browser Instance

In case of execution on Remote Browser Instance, you need to provide details regarding the remote browser instance when configuring Desired Capabilities.

Where:

  • Debugging Host: the host of the browser instance.
  • Debugging Port: the port that the browser instance uses to broadcast its activities.

 

Custom Execution

Custom execution is a bit different from other execution settings. Follow these steps to create a custom execution with its desired capabilities:

  1. Click the Add button of command toolbar above the custom execution list.
  2. A custom execution will be added to the list
  3. Change the name if needed, then click on the More icon under Value column
  4. The Custom Execution Configuration Builder dialog will be displayed. Specify the Driver Type for your custom execution. 

    You can have at most one web driver and one mobile driver here (because there will be potential conflict if multiple web drivers or multiple mobile drivers are used in the same test execution).

  5. Click on the More icon under Preferences column
  6. The Driver Builder dialog will be displayed. This is the form to set Desired Capabilities for the selected Driver. The steps to add new Desired Capabilities here is similar to other settings above.
  7. Click OK when you're done.

 

Location of Desired Capabilities files

Defined configuration settings are saved in separated files under the “<your test project location>\settings\internal” location (or “<your test project location>\settings\external\execution” in case of custom execution), as below:

Driver

Settings’ file

Chrome

com.kms.katalon.core.webui.chrome.properties

Firefox

com.kms.katalon.core.webui.firefox.properties

IE

com.kms.katalon.core.webui.ie.properties

Safari

com.kms.katalon.core.webui.safari.properties

Edge

com.kms.katalon.core.webui.edge.properties

Remote Webcom.kms.katalon.core.webui.remote.properties

Android

com.kms.katalon.core.mobile.android.properties

iOS

com.kms.katalon.core.mobile.ios.properties

  • No labels