The server is configured with environment variables. Set them before npm start, or,
on a Linux server installed with the deployment scripts, in /etc/autotestx.env
followed by sudo systemctl restart autotestx.
Interface to listen on. Keep 127.0.0.1 behind a reverse proxy.
PORT
4100
Port to listen on
ATX_PUBLIC_URL
http://HOST:PORT
The address people use to reach AutoTestX, e.g. https://autotestx.example.com. Password-reset links are built from it, never from the request’s Host header. An https: value also turns on secure cookies.
ATX_SECURE_COOKIES
off
1 forces the Secure flag on session cookies (automatic when ATX_PUBLIC_URL is https)
Browser pages kept warm for interactive runs. Opening a new page is the slowest part of starting a run (several seconds); a warm pool makes runs start almost instantly. Each page costs memory: use 1 on a 2 GB server.
ATX_MAX_ROW_CONCURRENCY
4
Platform ceiling on parallel rows in a data-driven run, whatever the test asks for. Use 2 on a 4 GB server.
ATX_HEADED
off
1 shows the browser for every server-side run (debugging on a desktop)
Where visible browsers open. local: on the server’s own screen. agent: on the tester’s computer through the AutoTestX Agent (use for any hosted server). auto: the agent when the user has one connected, otherwise the server’s screen.
ATX_AGENT_EXE
packages/agent/dist/AutoTestX-Agent.exe
The agent installer offered at /api/agent/download
The 2 GB and 4 GB values come from the deployment defaults. Memory per browser context
depends heavily on the application under test, so watch the server’s memory under a
realistic data-driven run before raising them.