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.
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.
To create a Web Test Case, perform the following steps:
From the Cyara Sidebar, select Build and then click the
New Test Case menu item. A screen as shown below is
- Select the Channel as Web. The relevant Web Test Case fields appear as shown in the screenshot.
- Enter a unique name for the Test Case in the Name field.
- Browse and select the Folder Path where the Test Case will be stored.
Enter a description of the Test Case in the
Use the drag handle that appears in the bottom right corner.
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.
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:blankUrl in Web Test Cases.
- 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
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.
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.
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
- Enter any notes for the Test Case in the Notes field.
Proxy Settings. If you choose
YES, the following screen appears.
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.
- Enter the Address.
- Enter the Username and Password.
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.
- If you choose Data Driven as YES, the options shown below appear:
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.
- 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 Pro
- Blackberry PlayBook
- Nexus 10
- Nexus 7
- Galaxy Note 3
- Galaxy Note II
- Laptop with touch
- Laptop with HiDPI screen
- Laptop with MDPI screen
- 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
- Browser = Chrome
- Location = lat, long