Overview
In today’s web-centric world, applications are accessed from a variety of devices and screen sizes—desktops, tablets, and smartphones. To ensure consistency and responsiveness across these different viewports, test automation must support scenarios that accurately emulate real-world usage.
ACCELQ offers Emulated Devices to tackle these requirements without needing physical device labs. This feature is especially useful if your team aims to:
- Accelerate testing by eliminating the complexity of managing multiple physical devices.
- Reduce costs associated with acquiring and maintaining device farms.
- Maintain comprehensive coverage across different breakpoints with minimal overhead.
Note: Emulated devices in ACCELQ are applicable only to web testing scenarios.
Use Cases for Emulated Devices
Web Recorder
- When recording or playing back your test logic, you can select an emulated device to simulate that device’s screen resolution.
- This ensures the elements you interact with during recording match the actual layout on the chosen device.
Test Run Kickoff
- At the start of a test run, choose the specific emulated device(s) to run against.
- Your tests then execute under realistic viewport conditions, allowing you to catch any resolution-specific issues early.
Central Device Management
ACCELQ provides a centralized location to manage all your emulated devices within the Resources section. This approach makes it easy for both technical and non-technical team members to:
- View all configured devices in one place.
- Create new device configurations without diving deep into technical details.
- Edit or Delete devices based on project needs or updated test requirements.
Steps to Manage Emulated Devices
-
Open Emulated Devices
- Navigate to Resources > Emulated Devices.
- A list of all existing devices is displayed, making it simple to assess your current coverage.
-
Add a New Device
- Click Add Device.
- Enter following information for the device being emulated:
- Width
- Height
- Device pixel ratio
- User Agent string: The User Agent string allows servers to gather information about the client, such as browser type, version, and device, to tailor their response and optimize rendering. This information can be found from various online resources, including websites with large collections of user-agent strings, such as this example site.
- Click Save to confirm.
-
Edit an Existing Device
- From the list, select the device to modify.
- Update the Name, Viewport dimensions, or other parameters.
- Click Save to apply changes.
-
Delete a Device
- Choose the device to remove.
- Click Delete, and confirm the action when prompted.
Best Practices
-
Use Descriptive Names
Label devices in a way that’s easily understood by your entire team (e.g., “iPhone 12 Portrait” instead of just “Mobile1”). -
Keep Dimensions Accurate
Align each device’s settings with real-world configurations to ensure authenticity in testing. -
Review Periodically
Remove or update devices that are no longer relevant, reducing clutter and confusion.
Additional Resources
- For a detailed guide on writing resolution-dependent tests, including how to use element instances and conditional logic, see Writing Resolution-Dependent Tests (Breakpoint Testing) in ACCELQ.
Comments
0 comments
Please sign in to leave a comment.