Test Studio Mobile allows the user to write tests on a desktop machine and then execute them on a mobile device. The communication between the desktop runner and the device's agent is based on exchanged JSON messages. A piece of sofware called Message Server is responsible for handling these messages.
The Message Server is a node.js application that starts automatically behind the scenes when Test Studio mobile project is opened in the Test Studio GUI. It runs on the same machine where Test Studio is run and can be accessed on the machine's host/IP address and port selected by the user - the default is 8084. Because message server is responsible for the entire communication between test runner and agents, Test Studio also connects to it right after a mobile project is opened.
In the Test Studio GUI, the message server current status can be verified at the bottom left corner. If, for some reason, Test Stuido can't connect to the message server, a red dot indicattor is presented. Click Edit Settings to show the Message Server Settings dialog where its host and port can be edited:
Enter valid and available host and port values and click the Restart button to restart and connection to the message server.
Message server settings can also be edited from the project settings dialog
The Message Server can be started even if Test Studio GUI doesn't run at all. The stand-alone version is include in the Mobile Runtime package and can be run on Windows, Mac and Linux machines:
- Download the Mobile Runtime package for the intended platform and unpack it.
- Open a command window and navigate to the unpacked folder location. Navigate to the
For Windows execute the
msgsrv-ctl.batfile. For Mac/Linux execute the
msgsrv-ctl.shfile. This will show you the available options for message server CLI.
startcommand will launch a stand-alone message server on the default port 8084.
The stand-alone Message Server CLI allows usage of any available port in the range bewteen 1025 and 65535. Just specify it as an option to the
The stand-alone version of the Message Server doesn't stop automatically. You will need to call the
stopcommand of the Message Server CLI after you finish your work with it. To check the current status of the server, call the CLI's