Web Driver Configuration for test executions (Profiles)

ACCELQ allows you to configure web driver capabilities to use for test execution. These configurations allow you to control browser startup behavior.

You can configure multiple Web Driver profiles and select one during test execution. For example, you may have a Driver Profile for running chrome in headless mode, and another one for setting browser window dimensions etc.

Create Web Driver Profile

You can create a Web Driver Profile from Resources tab in ACCELQ.

 

 

Provide a meaningful reference name and configuration text as input. Subsequent sections in this document describe the JSON format to use for Web Driver configuration. You can create multiple profiles to be used across the Project.

 

 

Configuration Format

Configuration JSON consists of three parts. All the capabilities and arguments use the standard Selenium Web Driver naming convention.

1. Browser binary path: Specifies the path to browser, in case it is not installed on standard system path.
2. Command line arguments to the browser: An array of capabilities are passed as browser startup arguments such as headless mode, incognito, window size, maximize window etc.
3. Web driver preferences such as download folder path etc.

 

An example below:

{

            "binary":"c:\\my programs\\Chrome\\chrome.exe",

            "args":["start-maximized", "incognito", "headless", "no-sandbox"],

 

Example: Setting binary path to a custom installed chrome browser

{
           "binary":"c:\\my programs\\Chrome\\chrome.exe"
}

 

Example: Running in headless mode

{
            "args":["headless"]
}

 

Example: Opening Chrome in incognito mode

{
            "args":["incognito"]
} 

 

Example: Setting up browser resolution

{
            "args":["window-size=2000,1600"]
}

 

Example: Invoke browser with a specific user's profile

Example: Turning off Browser notifications

{

    "prefs": { 
        "profile.default_content_setting_values.notifications":2
    }

}

Example: Enable BrowserStack Local Testing

{

  "browserstack.local":"true"

}

 

Example: To suppress certification (expired certificates) errors during test execution

{

"args":["--ignore-certificate-errors"]

}

 

Example: Saucelabs Configuration, when running tests against Saucelabs infra

{
  "extendedDebugging": "true",
  "capturePerformance": "true",
  "tunnelIdentifier": "<sauce_tunnel_name>",
  "parentTunnel":"<sauce_parent_tunnel_name>",
  "name": "<name_for_sauce_job_and_performance_capture_name>",
  "chromeOptions":{
    "args": ["window-size=2000,1600"],
    "prefs": {
       "pdfjs.disabled":"true"
     }
  }
} 

 

Using a Web Driver Profile for Test Execution

You can specify the Web Driver Profile to use, when running the test. In the Run Modal, click on the section that displays Browser and OS icons. Expanded panel displays a dropdown to select the profile. If you choose not to use any special profile, just select None.

Selected Profile is saved in user cache and the Run modal always opens with this profile pre-selected.

 

 

What Configuration was used for a Test Run

Test Report displays the configuration that was used for a particular test run. Simply click on the "configuration" link in the summary section of your test run report.

 

 

Custom Driver Profile for Playback

You can select a custom Web Driver Profile in the Playback settings. This will allow you to control the browser invocation behavior for the embedded Recorder browser.

It is important to note that certain device-related settings specified in the Web Driver profile will be ignored when used for the Recorder browser. In addition, the Recorder browser always opens in headless mode.

The following settings from the Web Driver profile are ignored in Recorder browser.

• Device width and height
• Device pixel ratio
• User-agent string