Robot Framework跨测试套件共享值：Linux环境适配及多实现方案

Great question! Sharing values across test suites in Robot Framework on Linux is a common requirement, and there are several solid approaches depending on your use case. Let's break them down with concrete examples and Linux-specific notes:

This is the most straightforward method for sharing static or pre-configured values. You define variables in a dedicated file, then import it into all test suites that need access.

Steps: #

• Create a variable file (e.g., global_vars.py or global_vars.resource)

  # global_vars.py
  SHARED_USERNAME = "test_user"
  SHARED_TOKEN = "abc123xyz"
  

• Import the file in each test suite:

  *** Settings ***
  Variables    /path/to/global_vars.py  # Use absolute path on Linux to avoid confusion
  

Linux-specific Notes: #

• Always use absolute paths (like /home/user/tests/global_vars.py) instead of relative paths if you're running tests from different directories.
• Ensure the file has read permissions for the user running the tests (chmod 644 global_vars.py if needed).

If you need to share dynamic values generated during test execution, Set Global Variable makes variables accessible across all test suites run in the same session.

Example: #

Suite 1 (sets the variable):

*** Test Cases ***
Set Shared Value
    ${dynamic_value}=    Generate Random String    10
    Set Global Variable    ${SHARED_DYNAMIC_VALUE}    ${dynamic_value}

Suite 2 (uses the variable):

*** Test Cases ***
Use Shared Value
    Log    The shared value is: ${SHARED_DYNAMIC_VALUE}

Linux-specific Execution Tip: #

Run the suites in order so the variable is set before it's used:

robot suite1.robot suite2.robot

If you're using a test suite file (testsuites.robot), list Suite 1 first in the suite order.

For more control over value sharing (like validation or caching), wrap the logic in custom keywords stored in a resource file. This keeps your code DRY and reusable.

Steps: #

• Create a resource file (e.g., shared_resources.resource):

  *** Keywords ***
  Set Shared Value
    [Arguments]    ${key}    ${value}
    Set Global Variable    ${SHARED_${key}}    ${value}
  
  Get Shared Value
    [Arguments]    ${key}
    Return From Keyword    ${SHARED_${key}}
  

• Import the resource file in your test suites:

  *** Settings ***
  Resource    /path/to/shared_resources.resource
  

Usage Example: #

Suite 1:

*** Test Cases ***
Store User ID
    Set Shared Value    USER_ID    12345

Suite 2:

*** Test Cases ***
Retrieve User ID
    ${user_id}=    Get Shared Value    USER_ID
    Log    Retrieved user ID: ${user_id}

If you need values to persist across separate test runs (not just the same execution session), write them to a file. Linux makes this easy with file system operations.

Example with JSON: #

Suite 1 (writes to file):

*** Settings ***
Library    JSONLibrary

*** Test Cases ***
Save Shared Data
    ${data}=    Create Dictionary    username=test_user    token=xyz789
    Save JSON To File    ${data}    /tmp/shared_data.json  # /tmp is ideal for temp files on Linux

Suite 2 (reads from file):

*** Settings ***
Library    JSONLibrary

*** Test Cases ***
Load Shared Data
    ${data}=    Load JSON From File    /tmp/shared_data.json
    ${token}=    Get From Dictionary    ${data}    token
    Log    Token from file: ${token}

Linux-specific Notes: #

• Use /tmp for temporary files (they're automatically cleaned up by the system).
• Ensure the user has write permissions to the target directory (chmod 755 /path/to/dir if needed).

You can share values using system environment variables, which is useful if you need to integrate with other Linux tools or scripts.

Example: #

Suite 1 (sets the env var):

*** Settings ***
Library    OperatingSystem

*** Test Cases ***
Set Env Variable
    Set Environment Variable    ROBOT_SHARED_VALUE    "my_shared_value"

Suite 2 (reads the env var):

*** Settings ***
Library    OperatingSystem

*** Test Cases ***
Get Env Variable
    ${shared_val}=    Get Environment Variable    ROBOT_SHARED_VALUE
    Log    Value from env var: ${shared_val}

Linux-specific Note: #

If you're running suites in separate terminal sessions, you'll need to export the variable first (e.g., export ROBOT_SHARED_VALUE="my_val"), but for suites run in the same robot command, the above works directly.

Quick Comparison of Approaches #

内容的提问来源于stack exchange，提问作者Arshpreet Singh