Skip to main content

Welcome to the Cyara Knowledge Center

Search

Creating a Web Test Case

Updated: tech writers Edited:

Before you begin to create the Test Case, you need to identify the actions a user would perform during a Web session. These actions can be related through a series of function calls.

For example, scripting a web browser can be complicated, requiring some knowledge of HTML, Javascript, and the browser DOM (Document Object Model). To facilitate the scripting process, Cyara provides a number of global function calls. See the Expect/Reply Types section for more information.

Also, ensure that you have performed the Chrome settings provided at the end of this topic before creating a Web Test Case on mobile browsers.

Note: Web Test Case Results can also be downloaded as a .MP4 video file, which will show a recording of the steps the browser session took while running the Test Case. On the Windows 10 & 11 operating systems there is a known issue with .MP4 file playback with the "Film & TV" application. We recommend using the “Windows Media Player” application on both Windows 10 and Windows 11 operating systems to playback these files.

To create a Web Test Case, perform the following steps:

  1. From the Cyara Sidebar, select Build and then click the New Test Case menu item. A screen as shown below is displayed:

  2. Select the Channel as Web. The relevant Web Test Case fields appear as shown in the screenshot.
  3. Enter a unique name for the Test Case in the Name field.
  4. Browse and select the Folder Path where the Test Case will be stored.
  5. Enter a description of the Test Case in the Description field.
    Use the drag handle that appears in the bottom right corner.
  6. Enter the URL. This is the full URL of the page that will be loaded to start the Web session. It should contain the scheme (HTTP or HTTPS) and be accessible by the Web Chat environment.

    • Note: To support Web Test Cases that do not exercise a web site (such as REST or Chat Bot tests) you can now use the empty about:blank Url in Web Test Cases.
  7. Select an optional Message Resolver from the drop-down list. The Message Resolver is a predefined script (made up of one or more function calls) that facilitates the Message Expect/Reply types. This is an optional step, leave this selection as is to use the default message resolver.
    See the Expect/Reply Types section for more information on the Message Resolver.
  8. Specify the Attributes. The Attributes section allows you to define any number of custom attributes that can be used by the Coordinator, Test Runner, or executing script. To enter a Test Case Attribute:
    • Enter the Key and specify a Value.
    • Click the + sign to add these values.
    Table 1. Currently Supported Attributes
    Key Description Value
    Width Specify the width of the browser Numeric, defaults to 1024
    Height Specify the height of the browser Numeric, defaults to 768
    Intercept.[relative path to resource] Overwrite the resource specified. Uses a URL relative to the current document Javascript or CSS styles to overwrite the target resource
    Intercept.[absolute path to resource] Overwrite the resource specified. Uses an absolute URL to the resource to replace Javascript or CSS styles to overwrite the target resource
    Browser Choose an alternate browser vendor for executing the Test Case Chrome
    Emulate Emulate a mobile browser while using Chrome (Browser must be set to Chrome) For the list of valid values, see the Configure Chrome for Web Test Cases section below.
    UserAgent Choose a different user agent string with which to identify the Browser which may impact server side code
    Location To allow a Test Case to be able to spoof its location so that Web sites can act upon its location. lat, long
    EnableConsoleLogging Set this attribute to False to disable Console logging for this test case. This attribute will default to True. False, True
    DisableScreenshots Setting this attribute to True will disable the screenshot capture of the web test case steps as they are performed. This attribute will default to False. False, True
    DisableAudio Audio is blocked from sending to the browser client by default. For platforms such as Twilio browser audio is required. This can be enabled by setting this attribute to False.

    This attribute will default to True.

    		False, True
    DisableNotifications Similarly to the above, Notifications are also blocked. For platforms such as Twilio notifications are required. Browser notifications can be enabled by setting this attribute to False.

    This attribute will default to True.

    		False, True
    HttpHeaders A CSV list of header keys and values to append with each request. x-custom=true
    Secure.HttpHeaders A CSV List of header keys and values to append to each request, however unlike HttpHeaders these will be stored encrypted. Authorization=Basic username:password
  9. Enter any notes for the Test Case in the Notes field.
  10. Specify the Proxy Settings. If you choose YES, the following screen appears.

    • Enter the Address.
    • Enter the Username and Password.
    The Proxy Settings section allows you to define an address and credentials for a local proxy server that is used to connect to the Internet. These details will be used by the Test Runner so that its internal browser can communicate with the Internet.
  11. Select the Data Driven option. Data Driven Test Cases allow you to place different dynamic data for each session from the same Test Case. Certain fields in the Test Case can be made dynamic. For more information, see the Data Driven Test Cases section.
    • If you choose Data Driven as YES, the options shown below appear:

    • You can either choose Upload File or Dynamic Data Service. If you choose Upload File, then select the file.

    Pulse Alerts for Web Test Cases are configured through the Dashboard and User Alarm Profiles. See Creating an Alarm Profile for more information.

    After this, you need to associate Steps with the Test Case. See the Entering Web Test Case Steps topic for more information.

Configure Chrome for Web Test Cases

Web Test Cases can now be executed against Chrome. This enables mobile emulation testing to validate how a site renders on a mobile device.

To nominate Chrome as a browser, on your Test Case, add an attribute of Browser and a value of Chrome.

To enable mobile emulation for Chrome, create an attribute of Emulate with one of the possible values:
  • iPhone 4
  • iPhone 5/SE
  • iPhone 6/7/8
  • iPhone 6/7/8 Plus
  • iPhone X
  • BlackBerry Z30
  • Nexus 4
  • Nexus 5
  • Nexus 5X
  • Nexus 6
  • Nexus 6P
  • Pixel 2
  • Pixel 2 XL
  • LG Optimus L70
  • Nokia N9
  • Nokia Lumia 520
  • Microsoft Lumia 550
  • Microsoft Lumia 950
  • Galaxy S III
  • Galaxy S5
  • Kindle Fire HDX
  • iPad Mini
  • iPad
  • iPad Pro
  • Blackberry PlayBook
  • Nexus 10
  • Nexus 7
  • Galaxy Note 3
  • Galaxy Note II
  • Laptop with touch
  • Laptop with HiDPI screen
  • Laptop with MDPI screen
Note: There are a couple of caveats when using Chrome.
  • The emulation and browser can only be set once per Campaign. The first Test Case with these values set will be used for all subsequent tests within the Campaign
  • When using a proxy server using Chrome, you cannot use credentials
  • The Chrome browser needs to be installed on the same server as your Web Coordinator

Settings to allow Spoofing of Geographic Location

To allow a Test Case to be able to spoof its location so that Web sites can act upon its location, enable the following attributes on a Test Case:
  1. Browser = Chrome
  2. Location = lat, long
Note: This only works for sites using Http
Was this article helpful?
0 out of 0 found this helpful
Return to top

Related articles

Comments

0 comments

Please sign in to leave a comment.