Remote Testing with an attachable AUT

Overview¶

Suppose you want to do Remote Testing on a different machine, but you don't want Squish to end your AUT process after the test case has been executed. Then you will need an attachable AUT.

Registering the Attachable AUT¶

You will need to register the Attachable AUT in the squishserver.

If you are using the IDE you can do that in

Edit > Server Settings > Manage AUTs > Attachable AUTs

The name is just an identifier and should not be a path or anything more complex.

Should you prefer the command line, then you will need to execute a command for the squishserver that looks somewhat like this

squishserver --config addAttachableAUT <Identifier> [host:]port

The host is the IP of the machine where the attachable AUT is running and can be left out in this command, which registers the attachable AUT for localhost.

Port of the Attachable AUT

Do NOT use the port 4322, because it is the standard port of the squishserver.
Network sockets can only be used by one process at a time on the same machine.
If the port of the server was changed via the --port argument, the new selected port
should not be choosen.

Starting the Attachable AUT¶

To make an Application attachable it must be launched through the start*aut tool, which you can find in <SQUISHDIR>\bin.

If you need more information on how to start the AUT in an attachable state, you should take a look at our documentation here start*aut

This prepares the AUT for attaching through Squish when the test case execution is started.

Possible setups¶

There are two possible setups, depending on where the squishserver that serves the information about the AUT is located.

Either the squishserver is running on the same machine as the runner or on the remote machine with the AUT. Both setups have certain drawbacks and depending on your test environment one might be preferrable over the other.

Running squishserver local¶

This setup is preferable if you plan to reboot your remote machine during tests, as the connection between runner and server should never be severed during a test execution.

In the case where you are using the IDE to trigger your tests, you can either rely on the internal squishserver or start another local squishserver that you connect via Remote Testing in the IDE.

If you want to connect the IDE to the local server, you navigate to

Edit > Preferences > Squish > Remote Testing

uncheck the Checkbox there and input the correct port for your server, that you start in a terminal or shell, the host can stay as 'localhost' as the squishserver will be running on the same machine as the IDE.

Running squishserver remotely¶

This setup is preferable if you want to use the RemoteSystem API , this allows you to interact with the remote system from within the script code.

For this setup, some actions need to be performed on the remote side after the installation of the Squish tools.

You will need to edit the file:

<SQUISHDIR>\etc\squishserverrc

This file controls which IP addresses are allowed to contact the server. The information is read when the server is started.

When you drive tests from within the IDE and want to use the remote server for the AUT information, then you must again use Remote Testing in the IDE in

`Edit > Preferences > Squish > Remote Testing`

however in this case the host should be the IPv4 address of the machine that your squishserver is running on.

remote-testing