The secret passages – remote execution
On occasions, we want to run our tests in a remote browser rather than locally. Sometimes, we want to run them on a particular port of a machine.
This could be useful for many reasons, one of which is that we want to grant access from a particular IP range to a particular port on a particular server. This way, we could avoid setting tokens, headers, or cookies. It could also help us get a more secure and private connection for our tests, and allow us to open and close the port to run the tests only when needed.
Most of the time, we want to test on a specific device or against a device farm. We could own one or it could be from a third party (they will generally provide the syntax and parameters to test remotely on their devices).
When we use tools such as Appium, under the hood we open a server on a specific port on our local computer (by default, 4723) and by creating a session against it, we are ultimately using a remote browser...
