Standard WebSocket works fine when you’re testing locally. But move to a CI pipeline, a remote device farm, or any environment where test traffic crosses a network boundary and unencrypted communication becomes a real concern. Commands, game objects, screenshots: everything travels in plain text over WS.
WSS (Secure WebSocket) fixes that. It encrypts all communication between your test scripts and the application under test, making it the right choice any time your testing setup leaves the safety of a local machine.
This matters especially for teams working with sensitive game assets, proprietary content, or user data, where leaking test traffic isn’t just inconvenient, it’s a liability.
What’s supported
Secure WebSocket is available for AltTester® SDK NonGPL and requires a Pro or Enterprise license. It’s also supported for applications instrumented with the AltTester Unreal SDK.
How to get started
You’ll need a valid TLS certificate, and you’ll need to make sure WSS is enabled consistently across three places: the AltTester® Desktop server, your instrumented application, and your AltDriver initialization. The full walkthrough is in the demo below.
We put together a short demo that walks through the full setup – from loading the certificate to running a successful test over a secure connection. It’s the fastest way to see how everything fits together.
👉 Watch the full demo below.
Have questions about your specific setup, licensing, or Unity / Unreal SDK support? Get in touch with our team – we’re happy to help you get it running.