Configuration

Overview

This section is for administrators and advanced users configuring how Total Shift Left connects to backend services and routes outbound traffic for test execution.

If you’re looking for base URL/auth variables for test runs, start with Configuration fundamentals.

Server connection

The server connection defines how the UI (web or desktop) connects to the backend service responsible for:

• executing test runs
• storing results and logs
• managing sessions and project data
• processing AI test generation (if enabled)

When to reconfigure the server URL

Reconfigure only when necessary (it may reset or invalidate local configuration depending on deployment):

• migrating to a different server or environment
• switching from staging to production backend
• troubleshooting connectivity issues

Best practices

• Prefer HTTPS in production.
• Ensure the backend URL is reachable from the client network.
• Avoid changes during active or scheduled test runs.

Proxy settings

Use proxy settings when your network requires outbound traffic to flow through an approved gateway (enterprise firewalls, monitoring, restricted egress).

Configuration options

• Enable proxy for the relevant execution mode (where your tests run).
• Proxy authentication (commonly HTTP Basic auth) if the proxy requires credentials.

Best practices

• Validate proxy credentials before scheduled runs.
• Disable proxy when not required to reduce latency.
• Keep proxy secrets in an approved secret manager.

Related articles

• Debug logging
• Public API