Results Handling#

Overview#

Fuze™ Test generates structured test results for every test execution. These results include:

Pass/fail status
Execution metadata (timestamps, test IDs)
Errors or exception traces
Optional DUT feedback and measurement data

All results are stored in local files by default, with support for cloud upload or external integration.

Default Behavior#

When a test run is executed, Fuze automatically creates a session-specific results file:

./results/session_<timestamp>.json

This file is written by the PTA engine using:

with open(self.__getSessionResultsFile(sessionid), 'w+') as outfile:
    json.dump(results, outfile, indent=4, sort_keys=True)

Each entry contains the outcome of a test case, including metadata like duration, tool used, failure reason, etc.

Example output snippet:

{
    "session_id": "1683123792",
    "test_cases": [
        {
            "id": "tc_flash_stm32",
            "status": "PASS",
            "duration": 4.2,
            "logfile": "tc_flash_stm32.log"
        },
        {
            "id": "tc_boot_verify",
            "status": "FAIL",
            "error": "Timeout on GPIO signal",
            "duration": 10.1
        }
    ]
}

Customization#

To change result behavior, modify the results section of the config JSON:

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

Fields:

store_dir: Where results are written locally.
format: Currently supports json.
upload: Enable/disable cloud export.
remote_target: Bucket, SFTP path, or custom destination.

Logging and Verbosity#

The ptalogging module provides unified log output.

Console logs are immediate.
File logs are written per test or session.
Format includes timestamp, thread, line number.

You can enable debug mode with:

export FUZE_DEBUG=1

This activates detailed output in the logs and error traces.

Troubleshooting#

Check for malformed JSON or missing fields in config files.
Verify disk space in results/ directory.
Use validateSuite to check syntax before running:

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

Results Handling

Contents