Challenges in Remote Device Testing
Testing remote systems brings unique challenges. Where the local and remote system are not geographically co-located, interactive script recording and debugging can become both cumbersome and time-consuming. Existing remote desktop solutions bring problems of their own: interoperability of the controlled and controlling platform, compatibility of the test framework and remote control application, setup and configuration issues, and others. Accessing certain embedded or mobile devices may not even be possible.
How It Works
The Squish GUI Tester relieves each of these pain points, through a fully-integrated, one-click remote control solution for virtually any target.
When working with a remote Application Under Test (AUT), Squish allows you to stream the display of the remote device locally on your machine, in real-time. When interactively recording tests, you can, from within the remote viewer, actually pick UI objects for inspection, use the Squish Spy tool for setting up a verification point, preview the current AUT state during a debug session, and more.
The data required for this functionality is embedded within regular Squish communication, meaning the required effort to get started with remote testing should be, in most cases, just a click away.
Remote control was designed to streamline test development of virtually any target, including desktop computers, mobile devices and even embedded platforms.
Tutorials & Documentation
We wrote a tutorial on testing an In-Vehicle Infotainment system running on an embedded board, using remote control to record and refactor a representative GUI test. Follow along here.
Check out our documentation for a complete list of Squish settings related to remote control.
Find out what else is possible from the Qt offering that Squish is now part of