The Configuration section allows administrators and advanced users to manage connectivity between the platform components and define network routing rules for API test execution. Proper configuration ensures secure, reliable communication between the UI, backend services, and test environments.
1. Server Connection #
Overview #
The Server Connection setting defines how the application connects to the backend service that powers test execution, data storage, reporting, and AI processing.
| Field | Details |
|---|---|
| Backend Server | http://app.totalshiftleft.ai |
| Connection Status | Connected |
Purpose #
This configuration links the application interface (web or desktop) with the backend server where:
- Test runs are executed
- Results and logs are stored
- AI test generation is processed
- User sessions and project data are managed
Reconfigure Option #
The Reconfigure button allows you to change the backend server URL.
⚠️ Important Notice:
Reconfiguring will:
- Clear all saved configurations
- Disconnect the current session
- Require a fresh server connection setup
Use this option only when:
- Migrating to a different server or environment
- Switching from staging to production backend
- Troubleshooting connectivity issues
Best Practices #
- Ensure the backend URL is reachable over the network.
- Use HTTPS for secure production environments.
- Avoid reconfiguring during active test runs.
2. Proxy Settings #
Overview #
The Proxy Settings module enables routing API traffic through a proxy server for environments with network restrictions, firewalls, or monitoring requirements.
The platform supports separate proxy configurations for different execution modes.
Execution Modes #
| Mode | Description |
|---|---|
| ☁️ Backend Execution | Applies to all tests executed on the backend server (manual and scheduled runs). |
| 🖥️ Local Runner | Applies to tests executed locally via the desktop application. |
Configuration Options #
Enable Proxy #
Toggle this option to activate proxy routing for the selected execution mode.
Proxy Authentication #
- Uses HTTP Basic Authentication
- Required if the proxy server enforces credentials
Settings Actions #
| Action | Purpose |
|---|---|
| Save Settings | Applies the proxy configuration for the selected mode |
| Reset to Defaults | Restores original proxy settings |
How It Works #
- The system automatically chooses the correct proxy based on execution location.
- Backend tests use backend proxy rules.
- Local desktop tests use local proxy rules.
This ensures:
- Compliance with enterprise firewall policies
- Secure routing through monitoring gateways
- Controlled outbound traffic from testing environments
When to Use Proxy #
- Corporate networks with restricted internet access
- Security-controlled environments
- Testing APIs inside internal networks
- Logging or inspecting API traffic via proxy tools
Best Practices #
- Configure proxy for backend execution in enterprise deployments.
- Use local runner proxy when testing against internal APIs.
- Validate proxy credentials before running scheduled tests.
- Disable proxy if not required to avoid latency.
Summary #
The Configuration module ensures seamless communication between system components and external APIs. With proper server connection and proxy setup, organizations can run tests securely across distributed environments while complying with network and security policies.
