​

Test Environments

​

Access Path

• URL: /test-env-manager

​

Environment List

​

List Information

​

Action Buttons

​

Creating New Environment

​

Steps

1. Click the “Create Environment” button at the top of the page
2. Fill in the dialog:

3. Click “Create” to create

​

Naming Recommendations

• Development - Development environment
• Staging - Staging environment
• Production - Production environment
• QA - Quality Assurance environment

​

Editing Environments

​

Modifying Basic Information

1. Find the target environment in the environment list
2. Click the “Edit” button
3. Modify name or description
4. Click “Update” to save

​

Deleting Environment

1. Click the “Delete” button for the environment
2. Confirm delete operation

Note: Environments that are being used by test round templates may not be deletable

​

Environment Variable Management

​

Opening Variable Management

​

Variable Types

​

Adding Variables

1. Click the “Add Variable” button
2. Fill in variable information:

3. Click to confirm adding

​

Editing Variables

1. Find the target variable in the variable list
2. Click the “Edit” button to enter edit mode
3. Modify variable information
4. Click “Save” to save

​

Deleting Variables

1. Click the “Delete” button for the variable
2. Confirm delete operation

​

Saving Changes

​

Common Environment Variable Examples

​

API Related

API_BASE_URL: <host>
API_VERSION: v2
API_TIMEOUT: 30000

​

Authentication Related

AUTH_USERNAME: testuser
AUTH_PASSWORD: ******** (use Password type)
AUTH_TOKEN: ******** (use Password type)

​

Database Related

DB_HOST: localhost
DB_PORT: 5432
DB_NAME: test_db

​

Feature Flags

ENABLE_DEBUG: true
ENABLE_MOCK: false

​

Using Environment Variables

​

In Test Round Templates

1. When creating a test round template
2. Select environment in the “Environment” field
3. Template will use all variables from that environment

​

Referencing in Tests

• ${API_BASE_URL} - Reference API_BASE_URL variable
• ${AUTH_USERNAME} - Reference AUTH_USERNAME variable

​

Best Practices

​

Environment Isolation

• Create independent settings for each test environment (Dev/Staging/Prod)
• Avoid different environments sharing the same variables

​

Protecting Sensitive Information

• Use Password type to store sensitive information
• Do not expose sensitive content in descriptions

​

Naming Conventions

• Use uppercase letters and underscores: API_BASE_URL
• Add prefixes for categorization: DB_HOST, AUTH_TOKEN

​

Related Features

• Device Pool Management
• Test Round Templates