EMU

Note

User guide: Scopy Overview.

Note

Tester

Test Date

Scopy version

Plugin version (N/A if not applicable)

Comments

Test 1: Enable the emulator.

UID: TST.EMU.EN

Description: This test verifies if starting the emulator in Scopy works correctly.

Preconditions:

  • Scopy is installed on the system.

  • iio-emu is installed on the system.

  • OS: Windows, Linux-x86_64 (flatpak and appimage), Linux-arm64, Linux-arm32, macOS.

Steps:

  1. Open Scopy.

  2. Click on Add device (+) button.

  3. Click on Emulator tab.

  4. From “Device” dropdown select “adalm2000”.

  5. Click on Enable button.

    • Expected result: The IIO device tab is selected, and the URI “ip:127.0.0.1” is entered in the corresponding section.

    • Actual result:

  1. Close Scopy and open it again.

  2. Click on Add device (+) button.

  3. Click on Emulator tab.

    • Expected result: The “Device” dropdown is set to “adalm2000” and the “Enable” button is displayed.

Tested OS:

Comments:

Result: PASS/FAIL

Test 2: EMU is not installed.

UID: TST.EMU.NOT

Description: This test verifies if Scopy handles the situation correctly when the IIO emulator is not found.

Preconditions:

  • Scopy is installed on the system.

  • iio-emu is not installed on the system.

  • Modify the “iio_emu_path” preference from “preferences.ini” file with an invalid path (you can access the file through the Open button in the general preferences).

  • OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS.

Steps:

  1. Open Scopy.

  2. Click on Add device (+) button.

  3. Click on Emulator tab.

    • Expected result: All the components are disabled and the message “Can’t find iio-emu in the system!” is displayed.

    • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 3: Disable the emulator.

UID: TST.EMU.DIS

Description: This test verifies if stopping the emulator in Scopy works correctly.

Test prerequisites:
Preconditions:

  • Scopy is installed on the system.

  • iio-emu is installed on the system.

  • OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS.

Steps:

  1. Open Scopy.

  2. Click on Add device (+) button.

  3. Click on Emulator tab.

  4. From “Device” dropdown select “adalm2000”.

  5. Click on Enable button.

  6. Click on Emulator tab.

  7. Click on Disable button.

    • Expected result: The fields in this tab become editable, and the Enable button appears.

    • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 4: Disable the emulator while the emulated device is connected.

UID: TST.EMU.DIS_CONN

Description: The test verifies if Scopy handles the situation correctly when an emulated device is connected and the “iio-emu” process is stopped.

Test prerequisites:
Preconditions:

  • Scopy is installed on the system.

  • iio-emu is installed on the system.

  • OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS.

Steps:

  1. Open Scopy.

  2. Start the iio-emu process using “adalm2000” in the dropdown and “ip:127.0.0.1” as URI.

  3. Add the device in device browser.

  4. Connect to emu device.

  5. Click on Add device (+) button.

  6. Click on Emulator tab.

  7. Click on Disable button.

    • Expected result: The fields in this tab become editable, and the Enable button appears. After a few seconds, the device is disconnected.

    • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 5: Verify adalm2000 emu device.

UID: TST.EMU.EN_ADALM2000

Description: This test verifies if starting the emulator in Scopy works correctly (using adalm2000 device).

Test prerequisites:
Preconditions:

  • Scopy is installed on the system.

  • iio-emu is installed on the system.

  • OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS.

Steps:

  1. Open Scopy.

  2. Click on Add device (+) button.

  3. Click on Emulator tab.

  4. From “Device” dropdown select “adalm2000”.

  5. Click on Enable button.

  6. Click on Verify button.

    • Expected result: The compatible plugins page opens. The compatible plugins are: M2kPlugin (checked), ADCPlugin, DACPlugin, DataLoggerPlugin, DebuggerPlugin, RegmapPlugin.

    • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 6: Verify pluto emu device.

UID: TST.EMU.EN_PLUTO

Description: This test verifies if starting the emulator in Scopy works correctly (using pluto device).

Test prerequisites:
Preconditions:

  • Scopy is installed on the system.

  • iio-emu is installed on the system.

  • OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS.

Steps:

  1. Open Scopy.

  2. Click on Add device (+) button.

  3. Click on Emulator tab.

  4. From “Device” dropdown select “pluto”.

  5. Click on Enable button.

  6. Click on Verify button.

    • Expected result: The compatible plugins page opens. The compatible plugins are: ADCPlugin (checked), DACPlugin (checked), DataLoggerPlugin (checked), DebuggerPlugin (checked), RegmapPlugin (checked).

    • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 7: Verify pqm emu device.

UID: TST.EMU.EN_PQM

Description: This test verifies if starting the emulator in Scopy works correctly (using pqm device).

Test prerequisites:
Preconditions:

  • Scopy is installed on the system.

  • iio-emu is installed on the system.

  • OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS.

Steps:

  1. Open Scopy.

  2. Click on Add device (+) button.

  3. Click on Emulator tab.

  4. From “Device” dropdown select “pqm”.

  5. Click on Enable button.

  6. Click on Verify button.

    • Expected result: The compatible plugins page opens. The compatible plugins are: PQMPlugin (checked), ADCPlugin, DACPlugin, DataLoggerPlugin, DebuggerPlugin (checked).

    • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 8: Verify swiot_config emu device.

UID: TST.EMU.EN_SWIOT_CONFIG

Description: This test verifies if starting the emulator in Scopy works correctly (using swiot_config device).

Test prerequisites:
Preconditions:

  • Scopy is installed on the system.

  • iio-emu is installed on the system.

  • OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS.

Steps:

  1. Open Scopy.

  2. Click on Add device (+) button.

  3. Click on Emulator tab.

  4. From “Device” dropdown select “swiot_config”.

  5. Click on Enable button.

  6. Click on Verify button.

    • Expected result: The compatible plugins page opens. The compatible plugins are: SWIOTPlugin (checked), DataLoggerPlugin, DebuggerPlugin (checked).

    • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 9: Verify swiot_runtime emu device.

UID: TST.EMU.EN_SWIOT_RUNTIME

Description: This test verifies if starting the emulator in Scopy works correctly (using swiot_runtime device).

Test prerequisites:
Preconditions:

  • Scopy is installed on the system.

  • iio-emu is installed on the system.

  • OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS.

Steps:

  1. Open Scopy.

  2. Click on Add device (+) button.

  3. Click on Emulator tab.

  4. From “Device” dropdown select “swiot_runtime”.

  5. Click on Enable button.

  6. Click on Verify button.

    • Expected result: The compatible plugins page opens. The compatible plugins are: SWIOTPlugin (checked), ADCPlugin, DataLoggerPlugin, DebuggerPlugin (checked), RegmapPlugin.

    • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 10: Verify generic emu device.

UID: TST.EMU.EN_GENERIC

Description: This test verifies if starting the emulator in Scopy works correctly (using generic device).

Test prerequisites:
Preconditions:

  • Scopy is installed on the system.

  • iio-emu is installed on the system.

  • OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS.

Steps:

  1. Open Scopy.

  2. Click on Add device (+) button.

  3. Click on Emulator tab.

  4. From “Device” dropdown select “generic”.

  5. Click on Enable button.

  6. Click on Verify button.

    • Expected result: The message “ip:127.0.0.1” not a valid context! is displayed.

    • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL