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.
To create a Web Test Case, perform the following steps:
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
- 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
Comments
0 comments
Please sign in to leave a comment.