Configuring Fuze™ Test

Configuring Fuze™ Test#

Introduction#

Fuze™ Test uses structured JSON configuration files to describe system setup, including bridges, DUT farms, acquisition tools, and result handling. These files are loaded at runtime and passed into the test adapter engine.

This document outlines each major system component and how to configure it.

Configuration File Format#

All configuration files are JSON-based. They are passed into the ProductTestAdapter via command line interface or test harness.

Example entrypoint usage:

python product-test-adapter.py --cmd startTest --config testbed_config.json

A typical top-level config might include sections like:

{
    "cloud2lab": { "hostname": "bridge.lab", "port": 5020 },
    "dut_farm": [
        { "id": "dut1", "ip": "192.168.1.101", "platform": "STM32" }
    ],
    "acquisition": {
        "serial_ports": ["/dev/ttyUSB0"],
        "gpio_controller": "pi4"
    },
    "results": {
        "store_dir": "./results/",
        "format": "json",
        "upload": false
    }
}

Configuring Cloud2Lab Bridge#

This section defines the gateway between cloud-side test orchestration and the local testbed.

{
    "cloud2lab": {
        "hostname": "bridge.lab.internal",
        "port": 5020,
        "auth_token": "ABC123XYZ"
    }
}

  • hostname: DNS name or IP of bridge endpoint.

  • port: Port to connect to.

  • auth_token (optional): Used for secure registration.

Configuring DUT Farm#

Defines the pool of DUTs (Devices Under Test) available to the testbed.

{
    "dut_farm": [
        {
            "id": "dut1",
            "ip": "192.168.1.101",
            "platform": "STM32F4",
            "slots": 4
        }
    ]
}

  • id: Logical name for DUT.

  • ip: Network address.

  • platform: Descriptive string.

  • slots: Number of parallel apps or ports.

Configuring Control and Acquisition#

This section defines how Fuze will interact with DUTs via hardware interfaces.

{
    "acquisition": {
        "serial_ports": ["/dev/ttyUSB0", "/dev/ttyUSB1"],
        "gpio_controller": "pi4",
        "can_interface": "can0"
    }
}

  • serial_ports: List of serial devices.

  • gpio_controller: Identifier for GPIO device.

  • can_interface: CAN bus interface name.

Configuring Results Handling#

Controls how results are stored, formatted, and uploaded.

{
    "results": {
        "store_dir": "./results/",
        "format": "json",
        "upload": true,
        "remote_target": "s3://fuze-results/"
    }
}

  • store_dir: Local path.

  • format: “json”, “xml”, or “html”.

  • upload: Boolean flag.

  • remote_target: Cloud bucket, FTP path, or SQL endpoint.

Validation and Debugging#

  • Ensure all config files are valid JSON.

  • Use –config yourfile.json to test parsing.

  • Enable verbose logs via env var: export FUZE_DEBUG=1

Contents