diff --git a/testing_results/testing_results_v2.0.0/general/core/add_dev_tests.rst b/testing_results/testing_results_v2.0.0/general/core/add_dev_tests.rst new file mode 100644 index 0000000000..d76f403cbc --- /dev/null +++ b/testing_results/testing_results_v2.0.0/general/core/add_dev_tests.rst @@ -0,0 +1,550 @@ +.. _add_dev_tests: + +Add device +========== + +.. note:: + + User guide: :ref:`Scopy Overview `. + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - Popa Andrei + - 18.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on Windows 10 + * - Danila Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on macOS 14.5 + +Setup environment: +------------------ + +.. _m2k-emu-add: + +**M2k.Emu:** + - Open Scopy. + - Start the iio-emu process using "adalm2000" in the dropdown and + "ip:127.0.0.1" as URI. + +Test 1: Verifying the device scanning functionality. +---------------------------------------------------- + +**UID:** TST.ADD.SCAN_ALL + +**Description:** This test checks that the device scan correctly detects and +lists available devices when initiated. + +**Preconditions:** + - Scopy is installed on the system. + - OS: ANY. + +**Steps:** + 1. Connect an **ADALM2000** device to the system by USB. + 2. Open Scopy. + 3. Click on **Add device** (+) button. + 4. Click on the refresh button on the right located in the **Add page** scan + section. + 5. Wait until the refresh animation stops. + - **Expected result:** In the "Context" dropdown, all available devices + are listed, each item containing the device name/description and URI. The + **ADALM2000** device [usb] must appear in the list. + - **Actual result:** As expected + + .. + Actual test result goes here. + .. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + +Test 2: Verifying the local device scanning functionality. +---------------------------------------------------------- + +**UID:** TST.ADD.SCAN_LOCAL + +**Description:** This test checks that the device scan correctly detects and +lists available local devices when initiated. + +**Preconditions:** + - Scopy is installed on the system. + - There is at least one IIO device connected to the system that has local + backend. + - OS: ANY. + +**Steps:** + 1. Open Scopy. + 2. Click on **Add device** (+) button. + 3. Click on **local** checkbox located in the **Add page** scan section. + 4. Wait until the refresh animation stops. + - **Expected result:** In the "Context" dropdown, all available local + devices are listed, each item containing the device name/description and URI. + If there is no available device the "No scanned devices available!" message + is displayed. + - **Actual result:** Missing **local** checkbox on Windows 10 + + .. + Actual test result goes here. + .. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** Test only fails on Windows 10 + +.. + Any comments about the test goes here. + +**Result:** FAIL + +.. + The result of the test goes here (PASS/FAIL). + +Test 3: Verifying the ip device scanning functionality. +------------------------------------------------------- + +**UID:** TST.ADD.SCAN_IP + +**Description:** This test checks that the device scan correctly detects and +lists available ip devices when initiated. + +**Preconditions:** + - Scopy is installed on the system. + - There is at least one IIO device connected to the system that has ip + backend. + - OS: ANY. + +**Steps:** + 1. Open Scopy. + 2. Click on **Add device** (+) button. + 3. Click on **ip** checkbox located in the **Add page** scan section. + 4. Wait until the refresh animation stops. + - **Expected result:** In the "Context" dropdown, all available ip + devices are listed, each item containing the device name/description and URI. + If there is no available device the "No scanned devices available!" message + is displayed. + - **Actual result:** As expected + + .. + Actual test result goes here. + .. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + +Test 4: Verifying the usb device scanning functionality. +-------------------------------------------------------- + +**UID:** TST.ADD.SCAN_USB + +**Description:** This test checks that the device scan correctly detects and +lists available usb devices when initiated. + +**Preconditions:** + - Scopy is installed on the system. + - OS: ANY. + +**Steps:** + 1. Connect an **ADALM2000** device to the system by USB. + 2. Open Scopy. + 3. Click on **Add device** (+) button. + 4. Click on **usb** checkbox located in the **Add page** scan section. + 5. Wait until the refresh animation stops. + - **Expected result:** In the "Context" dropdown, all available usb + devices are listed, each item containing the device name/description + and URI. The **ADALM2000** device must appear in the list. + - **Actual result:** As expected + + .. + Actual test result goes here. + .. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + +Test 5: Verifying the serial device scanning functionality. +----------------------------------------------------------- + +**UID:** TST.ADD.SCAN_SERIAL + +**Description:** This test checks that the device scan correctly detects and +lists available serial devices when initiated. + +**Preconditions:** + - Scopy is installed on the system. + - There is at least one IIO device connected to the system that has serial + backend. + - OS: ANY. + +**Steps:** + 1. Open Scopy. + 2. Click on **Add device** (+) button. + 3. Click on the refresh button on the right located in the **Add page** + serial port section. + 4. Wait until the refresh animation stops. + - **Expected result:** In the "Name" dropdown, all available serial + devices are listed, each item containing the device name/description + and URI. If there is no available device the "No scanned devices + available!" message is displayed. + - **Actual result:** As expected + + .. + Actual test result goes here. + .. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + +Test 6: Scanning with no device. +-------------------------------- + +**UID:** TST.ADD.SCAN_EMPTY + +**Description:** This test checks whether an appropriate message is displayed +when no device is found. + +**Preconditions:** + - Scopy is installed on the system. + - OS: ANY. + +**Steps:** + 1. Run Scopy. + 2. Make sure that no devices using USB backends are connected to the system. + 3. Click on **Add device** (+) button. + 4. Click on **usb** checkbox located in the **Add page** scan section. + 5. Wait until the refresh animation stops. + - **Expected result:** The "No scanned devices available!" message is + displayed. + - **Actual result:** As expected + + .. + Actual test result goes here. + .. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + +.. _tst-add-verify: + +Test 7: Device validation. +-------------------------- + +**UID:** TST.ADD.VERIFY + +**Description:** This test verifies that the device validation works correctly. + +**Test prerequisites:** + - :ref:`TST.EMU.EN `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: ANY. + +**Steps:** + 1. Click on **Add device** (+) button. + 2. Introduce the "ip:127.0.0.1" URI. + 3. Click on **Verify** button. + - **Expected result:** A loading animation starts and after a short time + a page with device details and compatible plugins is displayed. + - **Actual result:** As expected + + .. + Actual test result goes here. + .. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + +Test 8: Verify the "BACK" button from compatible plugin page. +------------------------------------------------------------- + +**UID:** TST.ADD.PLUGINS_BACK + +**Description:** This test checks if the **BACK** button works correctly. + +**Test prerequisites:** + - :ref:`TST.ADD.VERIFY `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: ANY. + +**Steps:** + 1. Click on **Add device** (+) button. + 2. Introduce the "ip:127.0.0.1" URI. + 3. Click on **Verify** button. + 4. Click on **BACK** button. + - **Expected result:** The verify page is displayed. + - **Actual result:** As expected + + .. + Actual test result goes here. + .. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + +.. _tst-add-plugins-add: + +Test 9: Verify the "ADD DEVICE" button from compatible plugin page (single plugin). +----------------------------------------------------------------------------------- + +**UID:** TST.ADD.PLUGINS_ADD_SINGLE + +**Description:** This test checks if the **ADD DEVICE** button works correctly. +Only the main plugin of the device is used. + +**Test prerequisites:** + - :ref:`TST.ADD.VERIFY `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: ANY. + +**Steps:** + 1. Click on **Add device** (+) button. + 2. Introduce the "ip:127.0.0.1" URI. + 3. Click on **Verify** button. + - **Expected result:** Only the M2kPlugin should be selected in the + compatible plugins section. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 4. Click on **ADD DEVICE** button. + - **Expected result:** The device is added to the device browser, the + device's info page is displayed, and the m2k tools are added to the + tool menu. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + +Test 10: Verify the "ADD DEVICE" button from compatible plugin page (multiple plugins). +--------------------------------------------------------------------------------------- + +**UID:** TST.ADD.PLUGINS_ADD_MULTIPLE + +**Description:** This test checks if the **ADD DEVICE** button works correctly. +Multiple plugins are used. + +**Test prerequisites:** + - :ref:`TST.ADD.VERIFY `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: ANY. + +**Steps:** + 1. Click on **Add device** (+) button. + 2. Introduce the "ip:127.0.0.1" URI. + 3. Click on **Verify** button. + - **Expected result:** Only the M2kPlugin should be selected in the + compatible plugins section. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 4. Select the DebuggerPlugin. + 5. Click on **ADD DEVICE** button. + - **Expected result:** The device is added to the device browser, the + device's info page is displayed, and all tools, including the debugger, are added + to the tool menu. + - **Actual result:** As expected + + .. + Actual test result goes here. + .. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + +Test 11: Verify the "ADD DEVICE" button from compatible plugin page with no plugin selected. +-------------------------------------------------------------------------------------------- + +**UID:** TST.ADD.PLUGINS_EMPTY + +**Description:** This test checks if the **ADD DEVICE** button works correctly. + +**Test prerequisites:** + - :ref:`TST.ADD.VERIFY `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: ANY. + +**Steps:** + 1. Click on **Add device** (+) button. + 2. Introduce the "ip:127.0.0.1" URI. + 3. Click on **Verify** button. + - **Expected result:** Only the M2kPlugin should be selected in the + compatible plugins section. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 4. Uncheck the M2kPlugin. + 5. Click on **ADD DEVICE** button. + - **Expected result:** A NO_PLUGIN device is added in device browser and + in tool menu. + - **Actual result:** As expected + + .. + Actual test result goes here. + .. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). diff --git a/testing_results/testing_results_v2.0.0/general/core/connection_tests.rst b/testing_results/testing_results_v2.0.0/general/core/connection_tests.rst new file mode 100644 index 0000000000..6f1217f6c5 --- /dev/null +++ b/testing_results/testing_results_v2.0.0/general/core/connection_tests.rst @@ -0,0 +1,279 @@ +.. _connection_tests: + +Connection flow +=============== + +.. note:: + + User guide: :ref:`Scopy Overview `. + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - Popa Andrei + - 18.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on Windows 10 + * - Danila Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on macOS 14.5 + +Setup environment: +------------------ + +.. _m2k-emu-conn: + +**M2k.Emu:** + - Open Scopy. + - Start the iio-emu process using "adalm2000" in the dropdown and + "ip:127.0.0.1" as URI. + - Add the device in device browser. + +.. _m2k-usb-conn: + +**M2k.Usb:** + - Open Scopy. + - Connect an **ADALM2000** device to the system by USB. + - Add the device in device browser. + +.. _tst-conn-succ: + +Test 1: Verify the connection flow. +----------------------------------- + +**UID:** TST.CONN.SUCC + +**Description:** This test checks if the **Connect** button works correctly. + +**Test prerequisites:** + - :ref:`TST.ADD.PLUGINS_ADD_SINGLE ` + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed in the system. + - Use :ref:`M2k.Emu ` setup. + - OS: ANY. + +**Steps:** + 1. Click on the device icon from device browser. + 2. Click on **Connect** button. + - **Expected result:** The **Disconnect** button appears, a status LED + is displayed under the icon in the device browser, and a progress bar + appears in the application's status bar. After a while, the connection + is established, the status LED turns green, and the tools in the menu + become accessible. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 2: Unplug the device while connecting (AUTO-SCAN). +------------------------------------------------------- + +**UID:** TST.CONN.UNPLUG_AUTO + +**Description:** This test verifies Scopy's behavior when the device is +unplugged during the connection process. + +**Test prerequisites:** + - :ref:`TST.HP.AUTO_SCAN_ON `. + +**Preconditions:** + - Scopy is installed on the system. + - The "Regularly scan for new devices" preference is enabled in the + preferences page. + - Use :ref:`M2k.Usb ` setup. + - OS: ANY. + +**Steps:** + 1. Click on the device icon from device browser. + 2. Click on **Connect** button. + 3. Unplug the device while connecting. + - **Expected result:** The device is removed from device browser. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 3: Unplug the device while connecting (MANUAL-SCAN). +--------------------------------------------------------- + +**UID:** TST.CONN.UNPLUG_AUTO + +**Description:** This test verifies Scopy's behavior when the device is +unplugged during the connection process. + +**Test prerequisites:** + - :ref:`TST.HP.MANUAL_SCAN `. + +**Preconditions:** + - Scopy is installed on the system. + - The "Regularly scan for new devices" preference is disabled in the + preferences page. + - Use :ref:`M2k.Usb ` setup. + - OS: ANY. + +**Steps:** + 1. Click on the device icon from device browser. + 2. Click on **Connect** button. + 3. Unplug the device while connecting. + - **Expected result:** A warning icon appears in the top-right corner + of the device in the device browser, and when hovered over, the + message "The device is not available! Verify the connection!" is + displayed. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 4: Unplug the device before connecting. +-------------------------------------------- + +**UID:** TST.CONN.UNPLUG_BEFORE + +**Description:** This test verifies Scopy's behavior when the device is +unplugged before the connection process. + +**Test prerequisites:** + - :ref:`TST.HP.MANUAL_SCAN `. + +**Preconditions:** + - Scopy is installed on the system. + - The "Regularly scan for new devices" preference is disabled in the + preferences page. + - Use :ref:`M2k.Usb ` setup. + - OS: ANY. + +**Steps:** + 1. Click on the device icon from device browser. + 2. Unplug the device. + 3. Click on **Connect** button. + - **Expected result:** The connection process starts but does not + complete. A warning icon appears in the top-right corner. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 5: Disconnecting a device. +------------------------------- + +**UID:** TST.CONN.DISCONN + +**Description:** This test checks if the **Disconnect** button works correctly. + +**Test prerequisites:** + - :ref:`TST.CONN.SUCC `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed in the system. + - Use :ref:`M2k.Emu ` setup. + - OS: ANY. + +**Steps:** + 1. Click on the device icon from device browser. + 2. Click on **Connect** button. + 3. Wait until the connection is done . + 4. Click on **Disconnect** button. + - **Expected result:** The device is disconnected, the **Connect** + button appears, the device remains in the device browser, and the + tools in the menu are no longer accessible. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). diff --git a/testing_results/testing_results_v2.0.0/general/core/dev_tests.rst b/testing_results/testing_results_v2.0.0/general/core/dev_tests.rst new file mode 100644 index 0000000000..d6ed75bb5f --- /dev/null +++ b/testing_results/testing_results_v2.0.0/general/core/dev_tests.rst @@ -0,0 +1,602 @@ +.. _dev_tests: + +Device interaction +================== + +.. note:: + + User guide: :ref:`Scopy Overview `. + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - Popa Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on Windows 10 + * - Danila Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on macOS 14.5 + +Setup environment: +------------------ + +.. _m2k-emu-dev: + +**M2k.Emu:** + - Open Scopy. + - Start the iio-emu process using "adalm2000" in the dropdown and + "ip:127.0.0.1" as URI. + - Add the device in device browser. + +.. _m2k-usb-dev: + +**M2k.Usb:** + - Open Scopy. + - Connect an **ADALM2000** device to the system by USB. + - Add the device in device browser. + +Test 1: Verifying the device button. +------------------------------------ + +**UID:** TST.HP.DEV_BTN + +**Description:** To verify that clicking on the device button triggers the +expected action: displaying device details and device tools. + +**Test prerequisites:** + - :ref:`TST.ADD.PLUGINS_ADD_SINGLE `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + +**Steps:** + 1. Click on the device icon. + 2. Observe the application's behavior. + - **Expected result:** The device details page is displayed in the + info page section, and in the tool menu (on the left), the device + is added with a list of available tools (in this form, the tools + cannot be accessed). + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 2: Remove a device from device browser. +-------------------------------------------- + +**UID:** TST.DEV.FORGET + +**Description:** This test checks if the "Forget" (x) button work correctly. + +**Test prerequisites:** + - :ref:`TST.ADD.PLUGINS_ADD_SINGLE `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + +**Steps:** + 1. Click the **Forget** button located at the bottom-right of the device icon. + - **Expected result:** The device is removed from device browser. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 3: Remove a device from device browser while it is connected. +------------------------------------------------------------------ + +**UID:** TST.DEV.FORGET_CONN + +**Description:** This test verifies whether Scopy properly handles the removal +of a connected device. + +**Test prerequisites:** + - :ref:`TST.CONN.SUCC `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + +**Steps:** + 1. Click on the device icon from device browser. + 2. Click on **Connect** button. + 3. Click the **Forget** button located at the bottom-right of the device icon. + - **Expected result:** Initially, the device is disconnected and then + successfully removed from the device browser. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 4: Edit the name of the device. +------------------------------------ + +**UID:** TST.DEV.EDIT_NAME + +**Description:** This test checks if the **Edit pen** button work correctly. + +**Test prerequisites:** + - :ref:`TST.ADD.PLUGINS_ADD_SINGLE `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + +**Steps:** + 1. Place the cursor in the top-right corner of the device icon in the + device browser. + 2. After the pen icon appears, click on it. + 3. Delete "M2k". + 4. Write "M3k". + 5. Press enter. + - **Expected result:** The device name changes both in the device + browser and in the tool menu. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 5: Select a tool. +---------------------- + +**UID:** TST.DEV.SELECT_TOOL + +**Description:** This test checks if the tool infrastructure works correctly. + +**Test prerequisites:** + - :ref:`TST.CONN.SUCC `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + +**Steps:** + 1. Click on the device icon from device browser. + 2. Click on **Connect** button. + 3. Click on "Oscilloscope" tool. + - **Expected result:** The "Oscilloscope" tool is displayed and the tool menu item is highlighted. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 4. Click on "Home" menu entry. + - **Expected result:** The device page is displayed and the home menu + item is highlighted. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +.. _tst-dev-detach-tool: + +Test 6: Detach a tool. +---------------------- + +**UID:** TST.DEV.DETACH_TOOL + +**Description:** This test checks if the tool detachment mechanism is working +correctly. + +**Test prerequisites:** + - :ref:`TST.CONN.SUCC `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + +**Steps:** + 1. Click on the device icon from device browser. + 2. Click on **Connect** button. + 3. Double click on "Oscilloscope" tool. + - **Expected result:** The "Oscilloscope" tool is integrated into a + separate window from the application. The window title should be: + "Scopy-M2kPlugin-Oscilloscope-ip:127.0.0.1". + + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 4. Close the "Oscilloscope" window. + - **Expected result:** The "Oscilloscope" tool is reintegrated into the main window. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 5. Detach the oscilloscope tool again. + 6. Close the application. + - **Expected result:** Scopy finished successfully. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 7: Reopen the app with a detached tool. +-------------------------------------------- + +**UID:** TST.DEV.DETACH_TOOL_RE + +**Description:** This test checks whether detached tools retain their state upon +reconnection. + +**Test prerequisites:** + - :ref:`TST.DEV.DETACH_TOOL `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - The application was previously closed with a detached tool (Oscilloscope). + - OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + +**Steps:** + 1. Click on the device icon from device browser. + 2. Click on **Connect** button. + - **Expected result:** The oscilloscope tool is detached. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 8: Collapse device tools in the tool menu. +----------------------------------------------- + +**UID:** TST.DEV.COLLAPSE + +**Description:** This test verifies if the collapse feature works properly in +the tool menu. + +**Test prerequisites:** + - :ref:`TST.ADD.PLUGINS_ADD_SINGLE `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - Use :ref:`M2k.Emu ` setup. + - OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + +**Steps:** + 1. Click on the device icon from device browser. + 2. Click on the device header from tool menu. + - **Expected result:** The tools collapse. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Repeat 2. + - **Expected result:** The tools expand. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +.. _tst-dev-multi-conn: + +Test 9: Connecting to multiple devices. +--------------------------------------- + +**UID:** TST.DEV.MULTI_CONN + +**Description:** This test checks if connecting to multiple devices is working +properly. + +**Test prerequisites:** + - :ref:`TST.CONN.SUCC `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - The "Connect to multiple devices" preference is enabled in the preferences + page. + - Use :ref:`M2k.Emu ` and :ref:`M2k.Usb ` setups. + - OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + +**Steps:** + 1. Click on the emu device icon from device browser. + 2. Click on **Connect** button. + - **Expected result:** The connection is established successfully. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Click on the usb device icon from device browser. + 4. Click on **Connect** button. + - **Expected result:** The connection is established successfully, both + device icons have a green status LED, both devices are entered into the + tool menu (the device header contains the device name and uri), and the + tools of each device can be accessed. If the menu contains too many + entries, then the scroll bar will become visible. + + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 10: Resource manager with multiple devices. +------------------------------------------------ + +**UID:** TST.DEV.RM_MULTI + +**Description:** This test verifies that the resource manager is being used +properly. + +**Test prerequisites:** + - :ref:`TST.DEV.MULTI_CONN `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - The "Connect to multiple devices" preference is enabled in the + preferences page. + - Use :ref:`M2k.Emu ` and :ref:`M2k.Usb ` setups. + - OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + +**Steps:** + 1. Click on the emu device icon from device browser. + 2. Click on **Connect** button. + 3. Click on the usb device icon from device browser. + 4. Click on **Connect** button. + 5. Click on the "Oscilloscope" run button of the emu device in the tool menu. + - **Expected result:** The button changes from stop button to run button (green color). + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 6. Click on the "Spectrum Analyzer" run button of the usb device in the tool menu. + - **Expected result:** The button changes from stop button to run button, + and the oscilloscope button (of the emu device) remains the same. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 11: Devices order in device browser. +----------------------------------------- + +**UID:** TST.DEV.ADD_ORDER + +**Description:** This test verifies that each newly added device is finally +entered into the device browser. + +**Test prerequisites:** + - :ref:`TST.ADD.PLUGINS_ADD_SINGLE `. + +**Preconditions:** + - Scopy is installed on the system. + - iio-emu is installed on the system. + - The "Connect to multiple devices" preference is enabled in the + preferences page. + - Use :ref:`M2k.Emu ` and :ref:`M2k.Usb ` setups. + - OS: Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + +**Steps:** + 1. Add the emu device. + 2. Add the usb device. + - **Expected result:** The usb device is on the right side of emu + device. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). diff --git a/testing_results/testing_results_v2.0.0/general/core/emu_tests.rst b/testing_results/testing_results_v2.0.0/general/core/emu_tests.rst new file mode 100644 index 0000000000..7e55ee4da6 --- /dev/null +++ b/testing_results/testing_results_v2.0.0/general/core/emu_tests.rst @@ -0,0 +1,501 @@ +.. _emu_tests: + +EMU +=== + +.. note:: + + User guide: :ref:`Scopy Overview `. + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - Popa Andrei + - 18.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on Windows 10 + * - Danila Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on macOS 14.5 + +.. _tst-emu-en: + +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, 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:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (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:** Emulator is still available (Windows 10, macOS 14.5) + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** Windows 10: With the iio-emu not installed in system and a bad preferences path, emulator is still found as long as iio-emu.exe is in the same folder as scopy.exe; macOS 14.5: Unable to locate the preferences.ini + +.. + Any comments about the test goes here. + +**Result:** FAIL + +.. + The result of the test goes here (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:** + - :ref:`TST.EMU.EN `. + +**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:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (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:** + - :ref:`TST.CONN.SUCC `. + +**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:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (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:** + - :ref:`TST.ADD.VERIFY `. + +**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:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (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:** + - :ref:`TST.ADD.VERIFY `. + +**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:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (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:** + - :ref:`TST.ADD.VERIFY `. + +**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. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (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:** + - :ref:`TST.ADD.VERIFY `. + +**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. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (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:** + - :ref:`TST.ADD.VERIFY `. + +**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, RegmapPlugin. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (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:** + - :ref:`TST.ADD.VERIFY `. + +**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:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). diff --git a/testing_results/testing_results_v2.0.0/general/core/hp_tests.rst b/testing_results/testing_results_v2.0.0/general/core/hp_tests.rst new file mode 100644 index 0000000000..589e9fdfd2 --- /dev/null +++ b/testing_results/testing_results_v2.0.0/general/core/hp_tests.rst @@ -0,0 +1,338 @@ +.. _hp_tests: + +Homepage +======== + +.. note:: + + User guide: :ref:`Scopy Overview `. + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - Popa Andrei + - 18.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on Windows 10 + * - Danila Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on macOS 14.5 + +Test 1: The homepage displays correctly when running the application. +--------------------------------------------------------------------- + +**UID:** TST.HP.RUN + +**Description:** This test checks if the homepage is displayed correctly. + +**Preconditions:** + - Scopy is installed on the system. + - OS: ANY. + +**Steps:** + 1. Open Scopy. + 2. Observe the application's behavior. + - **Expected result:** The application launches without errors and the + home page is displayed. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 2: Verifying the "Add device" (+) button. +---------------------------------------------- + +**UID:** TST.HP.ADD + +**Description:** This test checks if the **Add device** button works correctly. + +**Preconditions:** + - Scopy is installed on the system. + - OS: ANY. + +**Steps:** + 1. Open Scopy. + 2. Navigate to the application's home page. + 3. Click on the **Add device** button. + 4. Observe the application's behavior. + - **Expected result:** The page for adding a new device is displayed in + the info page section. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +.. _tst-hp-auto-scan-on: + +Test 3: Verifying the auto-scan feature (ON). +--------------------------------------------- + +**UID:** TST.HP.AUTO_SCAN_ON + +**Description:** This test checks if the auto-scan feature detects and lists all + available devices correctly. + +**Preconditions:** + - Scopy is installed on the system. + - The "Regularly scan for new devices" preference is enabled in the + preferences page. + - OS: ANY. + +**Steps:** + 1. Open Scopy. + 2. Ensure the **Scan** switch is enabled in the device browser section. + 3. Connect an **ADALM2000** device to the system by USB. + 4. Observe the application's behavior. + - **Expected result:** After a short period, the device appears in the + device browser section. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/ + +.. + The result of the test goes here (PASS/FAIL). + + +.. _tst-hp-auto-scan-off: + +Test 4: Verifying the auto-scan feature (OFF). +---------------------------------------------- + +**UID:** TST.HP.AUTO_SCAN_OFF + +**Description:** This test checks the behavior of the application when the auto- +scan is turned off. + +**Preconditions:** + - Scopy is installed on the system. + - The "Regularly scan for new devices" preference is enabled in the + preferences page. + - OS: ANY. + +**Steps:** + 1. Open Scopy. + 2. Ensure the **Scan** switch is disabled in the device browser section. + 3. Connect an **ADALM2000** device to the system by USB. + 4. Observe the application's behavior. + - **Expected result:** The device should not be visible in the device + browser. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +.. _tst-hp-manual-scan: + +Test 5: Verifying the manual scan feature. +------------------------------------------ + +**UID:** TST.HP.MANUAL_SCAN + +**Description:** This test checks if the manual scan feature detects and lists +all available devices correctly. + +**Preconditions:** + - Scopy is installed on the system. + - The "Regularly scan for new devices" preference is disabled in the + preferences page. + - OS: ANY. + +**Steps:** + 1. Open Scopy. + 2. Connect an **ADALM2000** device to the system by USB. + 3. Wait a few seconds to ensure that the connection has been successfully + established. + 4. Click on the **Scan** button. + 5. Observe the application's behavior. + - **Expected result:** The device appears in the device browser section. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 6: Navigation using the buttons in the info page. +------------------------------------------------------ + +**UID:** TST.HP.NAV + +**Description:** This test checks if the navigation buttons work correctly. + +**Test prerequisites:** + - :ref:`TST.HP.AUTO_SCAN_ON `. + +**Preconditions:** + - Scopy is installed on the system. + - OS: ANY. + +**Steps:** + 1. Open Scopy. + 2. Ensure the **Scan** switch is enabled in the device browser section. + 3. Connect an **ADALM2000** device to the system by USB. + 4. Wait until the device appears in device browser. + 5. Ensure that you are on "Welcome to Scopy" page. + 6. Click on the right arrow button. + - **Expected result:** The info page changes from the 'Welcome to Scopy' + page to the add page and in device browser the related button is + highlighted. + 7. Click on the left arrow button. + - **Expected result:** The "Welcome to Scopy" page is displayed and the + related button is highlighted. + 8. Click on the left arrow button. + - **Expected result:** The device's page is displayed and the device + icon is highlighted. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** Missing Actual result section in step 6 and 7 + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + +Test 7: Auto-scan behavior when the device is unplugged. +-------------------------------------------------------- + +**UID:** TST.HP.UNPLUGGED + +**Description:** This test checks if the auto-scan feature detects and lists all +available devices correctly. + +**Test prerequisites:** + - :ref:`TST.HP.AUTO_SCAN_ON `. + +**Preconditions:** + - Scopy is installed on the system. + - OS: ANY. + +**Steps:** + 1. Open Scopy. + 2. Ensure the **Scan** switch is enabled in the device browser section. + 3. Connect an **ADALM2000** device to the system by USB. + 4. Wait until the device appears in device browser. + 5. Unplug the device. + 6. Observe the application's behavior. + - **Expected result:** The device is removed from device browser. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). diff --git a/testing_results/testing_results_v2.0.0/general/core/install_tests.rst b/testing_results/testing_results_v2.0.0/general/core/install_tests.rst new file mode 100644 index 0000000000..93e8d0acae --- /dev/null +++ b/testing_results/testing_results_v2.0.0/general/core/install_tests.rst @@ -0,0 +1,468 @@ +.. _install_tests: + +Installers +=================================== + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - Popa Andrei + - 18.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on Windows 10 + * - Danila Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on macOS 14.5 + +Test 1: Check Scopy AppImage x86_64 +------------------------------------ + +**UID:** TST.START.APPIMAGE.X86_64 + +**Description:** This test verifies if the Scopy AppImage starts correctly on an +Linux Operating System with x86_64 architecture. + +**Preconditions:** + - OS: Linux intel x86_64 + - libfuse2 is required in order to execute an AppImage, install it using + **sudo apt-get install** + +**Steps:** + 1. Download Scopy Linux AppImage x86_64 from the `release page `_. + 2. Unzip the archive. + - **Expected result:** a file named **Scopy-x86_64.AppImage** should be extracted. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Grant execution permission to the file using the terminal. + + .. code-block:: shell + + chmod +x Scopy-x86_64.AppImage + + 4. To start the application execute the .AppImage file. + + .. code-block:: shell + + ./Scopy-x86_64.AppImage + + Or double-click from the GUI. + + - **Expected result:** A window containing the GUI of the application + should open and if opened from the terminal, the logs generated by the + application should be displayed inside the terminal. Inside the application, + a window containing the license agreement should appear with 2 buttons + "Exit" and "Continue". + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Press "Exit". + - **Expected result:** Scopy should gracefully close. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 6. Start again the application, just like in step 4. + 7. Press "Continue". + - **Expected result:** The window containing the license agreement + should close and Scopy should be still running. + - **Actual result:** + +.. + Actual test result goes here. +.. + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 2: Check Scopy AppImage arm32 +----------------------------------- + +**UID:** TST.START.APPIMAGE.X86_64 + +**Description:** This test verifies if the Scopy AppImage starts correctly on an +Linux Operating System with arm32 architecture. + +**Preconditions:** + - OS: Linux intel arm32 + - libfuse2 is required in order to execute an AppImage, install it using + **sudo apt-get install** + +**Steps:** + 1. Download Scopy Linux AppImage arm32 from the `release page `_. + 2. Unzip the archive. + - **Expected result:** a file named **Scopy-armhf.AppImage** should be extracted. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Grant execution permission to the file using the terminal. + + .. code-block:: shell + + chmod +x Scopy-armhf.AppImage + + 4. To start the application execute the .AppImage file. + + .. code-block:: shell + + ./Scopy-armhf.AppImage + + Or double-click from the GUI. + + - **Expected result:** A window containing the GUI of the application + should open and if opened from the terminal, the logs generated by the + application should be displayed inside the terminal. Inside the application, + a window containing the license agreement should appear with 2 buttons + "Exit" and "Continue". + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Press "Exit". + - **Expected result:** Scopy should gracefully close. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 6. Start again the application, just like in step 4. + 7. Press "Continue". + - **Expected result:** The window containing the license agreement + should close and Scopy should be still running. + - **Actual result:** + +.. + Actual test result goes here. +.. + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 3: Check if Scopy AppImage arm64 opens correctly +------------------------------------------------------- + +**UID:** TST.START.APPIMAGE.X86_64 + +**Description:** This test verifies if the Scopy AppImage starts correctly on an +Linux Operating System with arm64 architecture. + +**Preconditions:** + - OS: Linux intel arm64 + - libfuse2 is required in order to execute an AppImage, install it using + **sudo apt-get install** + +**Steps:** + 1. Download Scopy Linux AppImage arm64 from the `release page `_. + 2. Unzip the archive. + - **Expected result:** a file named **Scopy-arm64.AppImage** should be extracted. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Grant execution permission to the file using the terminal. + + .. code-block:: shell + + chmod +x Scopy-arm64.AppImage + + 4. To start the application execute the .AppImage file. + + .. code-block:: shell + + ./Scopy-arm64.AppImage + + Or double-click from the GUI. + + - **Expected result:** A window containing the GUI of the application + should open and if opened from the terminal, the logs generated by the + application should be displayed inside the terminal. Inside the application, + a window containing the license agreement should appear with 2 buttons + "Exit" and "Continue". + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Press "Exit". + - **Expected result:** Scopy should gracefully close. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 6. Start again the application, just like in step 4. + 7. Press "Continue". + - **Expected result:** The window containing the license agreement + should close and Scopy should be still running. + - **Actual result:** + +.. + Actual test result goes here. +.. + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 4: Check Scopy macOS +-------------------------- + +**UID:** TST.START.MACOS + +**Precondition:** + - OS: macOS intel + +**Description:** This test checks whether the Scopy macOS installer successfully +installs the application and ensures it launches correctly on a macOS operating +system with an x86_64 architecture. + +**Steps:** + 1. Download Scopy macOS installer from the release page. + 2. Unzip the archive. + - **Expected result:** A DMG file named **Scopy-macos** should be extracted. + (the file name will also contain the macOS version and the commit hash) + - **Actual result:** As expected. + +.. + Actual test result goes here. +.. + + 3. Double-click the file. + - **Expected result:** A pop-up that contains the Scopy icon will appear + - **Actual result:** As expected. + +.. + Actual test result goes here. +.. + + 4. Install the application by right clicking the file and click on **Open**. + - **Expected result:** A error pop-up will appear. + - **Actual result:** As expected. + +.. + Actual test result goes here. +.. + + 5. Click on **Cancel** and after that repeat the step 4, right click on the file, and click on **Open**. + - **Expected result:** A warning pop-up will appear. Different than + the first one by including an Open button. + - **Actual result:** As expected. + +.. + Actual test result goes here. +.. + + 6. Click on **Open** + - **Expected result:** After a while, a window with the GUI of the application + should open. Inside the application, a window containing the license + agreement should appear with 2 buttons "Exit" and "Continue". + - **Actual result:** As expected. + +.. + Actual test result goes here. +.. + + 7. Press "Exit". + - **Expected result:** Scopy should gracefully close. + - **Actual result:** AS expected. + +.. + Actual test result goes here. +.. + + 8. Start again the application by right-clicking and click on **Open**. + 9. Press "Continue". + - **Expected result:** The window containing the license agreement + should close and Scopy should be still running. + - **Actual result:** As expected. + +.. + Actual test result goes here. +.. + +**Tested OS:** macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 5: Check Scopy Windows installer +------------------------------------- + +**UID:** TST.START.WINDOWS + +**Precondition:** + - OS: Windows + +**Description:** This test checks whether the Scopy Windows installer successfully +installs the application and ensures it launches correctly on a Windows operating +system with an x86_64 architecture. + +**Steps:** + 1. Download Scopy Windows installer from the release page. + 2. Double-click the installer. + - **Expected result:** A window containing the installation wizard + should open. It should contain a drop-down menu from which can be + selected the language during the installation. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Click on **OK** + - **Expected result:** The installer continues with the `License Agreement` tab. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 4. Click on **I accept the agreement** and on **Next**. + - **Expected result:** The installer continues with the location where + the application will be installed. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 5. Select a location and click on **Next**. + - **Expected result:** The installer continues with the list of components + that will be installed. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 6. Click on **Next**. + - **Expected result:** The installer continues with the `Additional Tasks` tab. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 7. Check the `"Install drivers for ADALM2000 - Requires Administrative Rights"` box and click on **Next**. + - **Expected result:** The installer continues with the installation summary. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 8. Click on **Install**. + - **Expected result:** The application should start installing. At the end of + the installation, it should ask for Administrative Rights in order to install + ADALM2000 drivers. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 9. Inside the newly opened window. Follow the ADALM2000 drivers installation by clicking **Next** and **Finish**. + - **Expected result:** Both the application and the ADALM2000 drivers + installed successfully. And optionally, you can check to restart the + computer or not. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 10. Click on **Finish**. + +**Tested OS:** Windows 10 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). diff --git a/testing_results/testing_results_v2.0.0/general/core/license_about_page_tests.rst b/testing_results/testing_results_v2.0.0/general/core/license_about_page_tests.rst new file mode 100644 index 0000000000..d79400d9a6 --- /dev/null +++ b/testing_results/testing_results_v2.0.0/general/core/license_about_page_tests.rst @@ -0,0 +1,185 @@ +.. _license_and_about_page_tests: + +License and About Page +======================================== + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - Popa Andrei + - 18.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on Windows 10 + * - Danila Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on macOS 14.5 + +Test 1: Check license pop-up +----------------------------- + +**UID:** TST.LICENSE.POPUP + +**Preconditions:** + - OS: Any + +**Description:** This test verifies if the license pop-up appears at the start of the application. + +**Steps:** + 1. Start the Scopy application. + 2. Click on **Preferences** + 3. Scroll down, click on **Reset** and after that on **Restart** + - **Expected result:** The application should restart and the first thing + that appears on the screen is a pop-up regarding the license used in Scopy. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 4. Click on the highlighted text **"GPLv3"** + - **Expected result:** A web browser window will open containing the GPLv3 + license used by Scopy. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 5. Click on **Continue** + - **Expected result:** The application will display the home screen with + the text "Welcome to Scopy!". + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 2: Check links from About Page +------------------------------------- + +**UID:** TST.ABOUT.PAGE + +**Preconditions:** + - OS: Any + +**Description:** This test verifies if all the links from **About Page** work correctly. + +**Steps:** + 1. Start the Scopy application. + 2. Click on the **About** button from the bottom left side of the application. + - **Expected result:** The application will display a screen containing + textual information about the current version. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Click on the underlined word **here** from the line **Build info: here** + - **Expected result:** The displayed text will change, and it now shows + more detailed information about the building process. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 4. Click on the **Home** buttom from the top right side of the application. + - **Expected result:** The application will display the initial screen + of the About page. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 5. Click on the highlighted text **Scopy open source project** + - **Expected result:** The application will display more information about + the Scopy project. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 6. Click on the **Home** buttom from the top right side of the application. + 7. Click on the highlighted text **other open source software** + - **Expected result:** The application will display a list of open source + libraries included or linked to Scopy. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 8. Click on the **Home** buttom from the top right side of the application. + 9. Click on the highlighted text **Latest Release** + - **Expected result:** A web browser window will open containing the latest + release of Scopy. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 10. Click on the **Home** buttom from the top right side of the application. + 11. Click on the highlighted text **Documentation** + - **Expected result:** A web browser window will open containing the + documentation for Scopy. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 12. Click on the **Home** buttom from the top right side of the application. + 13. Click on the highlighted text **Support Forum** + - **Expected result:** A web browser window will open containing a forum + named `ADI EngineerZone`. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** Steps 10 and 12 are not needed since there is no need to press the home button + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). diff --git a/testing_results/testing_results_v2.0.0/general/general_preferences_tests.rst b/testing_results/testing_results_v2.0.0/general/general_preferences_tests.rst new file mode 100644 index 0000000000..c15decc856 --- /dev/null +++ b/testing_results/testing_results_v2.0.0/general/general_preferences_tests.rst @@ -0,0 +1,1099 @@ +.. _general_preferences_tests: + +General Preferences - Test Suite +================================== + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - Popa Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on Windows 10 + * - Danila Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on macOS 14.5 + +Setup environment: +------------------ + +.. _m2k_emu_setup: + +**M2K.emu:** + - Press the add device button + - Enable emulator for adalm2000 + - Verify and add device with M2KPlugin and ADCPlugin enabled + +.. _pluto_emu_setup: + +**Pluto.emu:** + - Press the add device button + - Enable emulator for pluto + - Verify and add device with ADCPlugin enabled + +.. _pluto_emu_usb_setup: + +**Pluto.usb:** + - Connect a pluto device via usb to your PC + - Connect to the device in Scopy with ADCPlugin enabled + + +Test 1 - Save/Load Scopy session +-------------------------------------------------- + +.. _TST.PREF.SAVE_LOAD_SESSION: + +**UID:** TST.PREF.SAVE_LOAD_SESSION + +**Description:** Manage sessions to retain or load overall application +states (only applies to plugins which have this implemented). + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`M2K.emu` + - OS: ALL + +**Steps:** + 1. Set preference to enabled + 2. Open Oscilloscope tool + 3. Modify the time base value to 1s + 4. Close Scopy + 5. Open the app using the same setup and check if the time base + - **Expected result:** time base is 1s + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 6. Redo all the steps with the preference disabled + - **Expected result:** time base is the default value + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 7. Press the "Settings file location" open button within the preference menu + - **Expected result:** should open a file browser containing + .ini files for every plugins' session saved + - **Actual result:** Nothing happens + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** Test only fails on macOS: Unable to locate the preferences.ini file on macOS when using the **Open** button. + +.. + Any comments about the test goes here. + +**Result:** FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 2 - Double click to attach/detach tool +-------------------------------------------------- + +.. _TST.PREF.DOUBLECLICK_ATTACH_DETACH: + +**UID:** TST.PREF.DOUBLECLICK_ATTACH_DETACH + +**Description:** Tools can be detached from the main window by +double clicking them in the left menu. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`M2k.emu` + - OS: ALL + +**Steps:** + 1. Set preference to enabled. + 2. Double click Oscilloscope tool to detach it. + - **Expected result:** Oscilloscope tool should detach from + the main window into a new one. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Redo all the steps with the preference disabled. + - **Expected result:** Nothing should happen. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 3 - Save/Load tool attached state +-------------------------------------------------- + +.. _TST.PREF.SAVE_LOAD_TOOL_STATE: + +**UID:** TST.PREF.SAVE_LOAD_TOOL_STATE + +**Description:** Manage sessions to retain tool attached states. + +**Test prerequisites:** + - Emulator tests + - Depends on :ref:`Test Double click to attach/detach tool` + +**Preconditions:** + - :ref:`M2k.emu` + - OS: ALL + +**Steps:** + 1. Set preference to enabled. + 2. Double click Oscilloscope tool to detach it. + 3. Close Scopy. + 4. Open the app using the same setup. + - **Expected result:** Oscilloscope is still detached. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 5. Redo all the steps with the preference disabled. + - **Expected result:** Oscilloscope should not be detached. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 4 - Double click control buttons to open menu +-------------------------------------------------- + +.. _TST.PREF.DOUBLECLICK_CONTROL_MENU: + +**UID:** TST.PREF.DOUBLECLICK_CONTROL_MENU + +**Description:** Open menu from MenuControlButtons by double clicking them. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ALL + +**Steps:** + 1. Set preference to enabled. + 2. Open ADC - Time tool. + 3. Double click Cursors button in the bottom right ( + do not click on the button's icon). + + - **Expected result:** A hovering menu should open above the button. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 4. Redo all the steps with the preference disabled. + - **Expected result:** No menu should open. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 5 - Enable OpenGL plotting +-------------------------------------------------- + +.. _TST.PREF.ENABLE_OPENGL_PLOTTING: + +**UID:** TST.PREF.ENABLE_OPENGL_PLOTTING + +**Description:** Use GPU acceleration for rendering plots (OpenGL-based). + +**Test prerequisites:** + - Emulator tests + - Depends on Test "Plot FPS" + +**Preconditions:** + - :ref:`M2k.emu` + - OS: ALL + +**Steps:** + 1. Set preference to enabled. + 2. Set Debug preference "Show plot FPS" to enabled. + 3. Open Oscilloscope tool and run it. + - **Expected result:** The red text inside the plot + should contain "OpenGL rendering." + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 4. Redo all the steps with the preference disabled. + - **Expected result:** The red text inside the plot + should contain "Software rendering." + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 6 - Enable menu animations +-------------------------------------------------- + +.. _TST.PREF.ENABLE_MENU_ANIMATIONS: + +**UID:** TST.PREF.ENABLE_MENU_ANIMATIONS + +**Description:** Toggle visual animations for menu transitions. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`M2k.emu` + - OS: ANY + +**Steps:** + 1. Set preference to enabled. + 2. Open Oscilloscope tool and toggle between trigger and channel menus. + - **Expected result:** Opening menus should be animated. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Redo all the steps with the preference disabled. + - **Expected result:** Opening menus shouldn't have any animations. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 7 - Enable the status bar for displaying important messages +----------------------------------------------------------------- + +.. _TST.PREF.ENABLE_STATUS_BAR: + +**UID:** TST.PREF.ENABLE_STATUS_BAR + +**Description:** Show status messages on the bottom of the app window. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`M2k.emu` + - OS: ANY + +Steps + 1. Set preference to enabled. + 2. Do the setup again and look for a message bar when pressing "connect." + - **Expected result:** A message about connecting should appear at the bottom of the window. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Redo all the steps with the preference disabled. + - **Expected result:** No message should pop up. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 8 - Show Grid +-------------------------------------------------- + +.. _TST.PREF.SHOW_GRID: + +**UID:** TST.PREF.SHOW_GRID + +**Description:** Display grid lines for better visual referencing on plots. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Set preference to enabled. + 2. Open ADC - Time tool. + - **Expected result:** A grid should be visible on the plot. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Redo all the steps with the preference disabled. + - **Expected result:** No grid on the plot. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 9 - Show Graticule +-------------------------------------------------- + +.. _TST.PREF.SHOW_GRATICULE: + +**UID:** TST.PREF.SHOW_GRATICULE + +**Description:** Display lines for axes centered on 0 points on plots. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Set preference to enabled. + 2. Open ADC - Time tool. + - **Expected result:** A horizontal and a vertical + measurement line should be centered on the 0-axis + points (both may not be visible at the same time). + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Redo all the steps with the preference disabled. + - **Expected result:** The lines should border the entire + plot instead of centering on 0 points. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 10 - Use Lazy Loading +-------------------------------------------------- + +.. _TST.PREF.USE_LAZY_LOADING: + +**UID:** TST.PREF.USE_LAZY_LOADING + +**Description:** Load IIO resources as needed to improve initial load performance. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: Windows + +**Steps:** + 1. Set preference to enabled. + 2. Open Scopy console executable. + 3. After connecting to Pluto as described in the setup, look + in the console for "device connection took:" times. + 4. Redo all the steps with the preference disabled and + compare the elapsed times. + + - **Expected result:** Elapsed times connecting to some + plugins should be lower when lazy loading is enabled. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 11 - Use native dialogs +------------------------------- + +.. _TST.PREF.USE_NATIVE_DIALOGS: + +**UID:** TST.PREF.USE_NATIVE_DIALOGS + +**Description:** Use system-native dialog windows. + +**Preconditions:** + - OS: ALL + +**Steps:** + 1. Set preference to enabled. + 2. Press the Load button on the left menu. + - **Expected result:** A native file browser window should open. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Redo all the steps with the preference disabled. + - **Expected result:** A non-native, Scopy-specific, + file browser window should open. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 12 - Auto-connect to previous session +-------------------------------------------------- + +.. _TST.PREF.AUTO_CONNECT_PREVIOUS_SESSION: + +**UID:** TST.PREF.AUTO_CONNECT_PREVIOUS_SESSION + +**Description:** Automatically reconnect to the last used devices on startup. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Set preference to enabled. + 2. Connect to the device and then close the application. + 3. Open Scopy. + - **Expected result:** Scopy should automatically connect + to the Pluto device. + - **Actual result:** Device does not automatically connect + +.. + Actual test result goes here. +.. + + 4. Redo all the steps with the preference disabled. + - **Expected result:** Should not connect automatically. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** Test fails only on Windows 10 + +.. + Any comments about the test goes here. + +**Result:** FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 13 - Font scale +-------------------------------------------------- + +.. _TST.PREF.FONT_SCALE: + +**UID:** TST.PREF.FONT_SCALE + +**Description:** Adjust font size within the app (this is experimental, +so some layout artifacts may appear). + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Set preference to 1.45, restart Scopy, and inspect some tools. + - **Expected result:** All app text and some buttons should be larger. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 2. Repeat the steps for font size 1. + - **Expected result:** Text should return to default size. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 14 - Theme +-------------------------------------------------- + +.. _TST.PREF.THEME: + +**UID:** TST.PREF.THEME + +**Description:** Change application theme. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Set preference to a different theme and restart the app. + - **Expected result:** Themes should change while retaining + the same UX and usability in all tools. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 15 - Language +-------------------------------------------------- + +.. _TST.PREF.LANGUAGE: + +**UID:** TST.PREF.LANGUAGE + +**Description:** Change the language of the application interface. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`M2k.emu` + - OS: ANY + +Steps + 1. Set preference to a different language and restart the app. + - **Expected result:** Some text language should change in the M2K tools. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** Most text is not translated + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 16 - Connect to multiple devices +-------------------------------------------------- + +.. _TST.PREF.CONNECT_MULTIPLE_DEVICES: + +**UID:** TST.PREF.CONNECT_MULTIPLE_DEVICES + +**Description:** Enable connections to multiple hardware and emulator + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` and :ref:`M2k.emu` + - OS: ANY + +**Steps:** + 1. Set preference to enabled. + 2. Connect to 2 devices following the setup. + - **Expected result:** Two devices should appear in the left + menu and be fully functional. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Repeat the steps with the preference disabled. + - **Expected result:** When connecting to the second device, + the first one should automatically disconnect. + - **Actual result:**As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 17 - Regularly scan for new devices +-------------------------------------------------- + +.. _TST.PREF.REGULARLY_SCAN_NEW_DEVICES: + +**UID:** TST.PREF.REGULARLY_SCAN_NEW_DEVICES + +**Description:** Continuously scan and recognize newly connected devices. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Connect the Pluto to the machine via USB. + - **Expected result:** Pluto should automatically appear in + the device list, and a toggle switch for scanning should + appear in the top right. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 2. Repeat the steps with the preference disabled. + - **Expected result:** Pluto should not appear automatically, + only when pressing the on-demand Scan button. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 18 - Session devices +-------------------------------------------------- + +.. _TST.PREF.SESSION_DEVICES: + +**UID:** TST.PREF.SESSION_DEVICES + +**Description:** Automatically connect to saved devices. + +**Preconditions:** + - :ref:`Pluto.usb` + - :ref:`"Auto-connect to previous session"` preference needs to be enabled + - OS: ANY + +**Steps:** + 1. After connecting to M2K, go to the preferences and press "Refresh." + 2. Check the current device's URI. + 3. Go back to the homepage and forget the device by pressing the red + "X" button on the device. + 4. Close and reopen Scopy. + - **Expected result:** Should automatically connect to the URI you + checked. + - **Actual result:** Device does not automatically connect + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** Test fails only on Windows 10 + +.. + Any comments about the test goes here. + +**Result:** FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 19 - Show plot FPS +-------------------------------------------------- + +.. _TST.PREF.SHOW_PLOT_FPS: + +**UID:** TST.PREF.SHOW_PLOT_FPS + +**Description:** Show FPS on plots. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`M2k.emu` and :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Open Oscilloscope and run it. + 2. Open ADC - Time and run it. + - **Expected result:** Should show the FPS on the plot + (M2K may look different from other plugins). + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Repeat the steps with the preference disabled. + - **Expected result:** No FPS should be visible. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 20 - Plot target FPS +-------------------------------------------------- + +.. _TST.PREF.PLOT_TARGET_FPS: + +**UID:** TST.PREF.PLOT_TARGET_FPS + +**Description:** Manage the maximum FPS plots should run at +(this may also affect the IIO acquisition). + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.usb` + - "Show plot FPS" needs to be enabled. + - OS: ANY + +**Steps:** + 1. Set the preference to each value and run ADC - Time to check FPS. + - **Expected result:** Plot FPS should be capped at the selected value. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + +Test 21 - Reset settings and plugins to default +-------------------------------------------------- + +.. _TST.PREF.RESET_SETTINGS_DEFAULT: + +**UID:** TST.PREF.RESET_SETTINGS_DEFAULT + +**Description:** Resets all settings and plugins to default values. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`M2k.emu` + - OS: ANY + +**Steps:** + 1. Change general preferences and M2K preferences. + 2. Press the "Restart" button and restart the app. + - **Expected result:** All changed preferences should have + the default values. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + + diff --git a/testing_results/testing_results_v2.0.0/general/index.rst b/testing_results/testing_results_v2.0.0/general/index.rst new file mode 100644 index 0000000000..6f638bc0cd --- /dev/null +++ b/testing_results/testing_results_v2.0.0/general/index.rst @@ -0,0 +1,27 @@ +.. _tests_general: + +General Test Cases +=============================================================================== + +Contents +--------------------------------------------------------------------- + +.. toctree:: + :includehidden: + :maxdepth: 3 + + core/hp_tests + core/license_about_page_tests + core/install_tests + core/add_dev_tests + core/connection_tests + core/emu_tests + core/dev_tests + + instrument_detaching_tests + general_preferences_tests + +.. + add the path to each core feature test case here + example core/homepage_tests + diff --git a/testing_results/testing_results_v2.0.0/general/instrument_detaching_tests.rst b/testing_results/testing_results_v2.0.0/general/instrument_detaching_tests.rst new file mode 100644 index 0000000000..6e5f3ccf16 --- /dev/null +++ b/testing_results/testing_results_v2.0.0/general/instrument_detaching_tests.rst @@ -0,0 +1,91 @@ +Instrument Detaching - Test Suite +==================================================================================================== + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - Popa Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on Windows 10 + * - Danila Andrei + - 19.02.2025 + - 2.0.0 a3a7c43 + - N/A + - Tested on macOS 14.5 + +General Description: + - The instrument detaching is the process of removing the instrument from the main window. This is usually done by double clicking the tool name from the tool menu (left side of scopy). The instrument detaching is useful when the user has multiple screens and wants to observe multiple instruments at the same time. The user can detach the instrument from the main window and move it to another screen or another part of the same screen. This feature is not available on Android. Any detached windows will be closed when the main window is closed. + - When detaching a window, the title bar will include the name of the detached instrument. The user can reattach the instrument either by clicking the X button from the detached window title bar or by double clicking the tool name from the tool menu. The minimize and maximize buttons are also available on the detached window title bar and should work as expected. When reattaching the instrument, the reattached instrument will be the one currently selected. The user can detach multiple instruments at the same time. The detached instruments will be displayed in the order they were detached. Every detached instrument will work exactly as if they were still attached to the main window. The user can detach any instrument that is not the last instrument in the main window. When restarting Scopy, all detached instruments will be detached, just like in the previous session. + +Setup enviroment: +---------------------------------------------------------------------------------------------------------------------------- + +.. _pluto-usb-instrument-detaching: + +**Pluto.Usb:** + - Open the Scopy application + - Connect the PlutoSDR to the computer via USB + - Type the URI of the PlutoSDR in the URI field (if you don't know the URI, just type "ip:192.168.2.1") + +Test 1: Detach and reattach an instrument +---------------------------------------------------------------------------------------------------- + +**UID:** TST.GEN.INST.DETACH_REATTACH + +**Description:** This test checks if the user can detach and reattach an instrument from the main window. The user can detach the instrument by double clicking the tool name from the tool menu (left side of scopy). The user can reattach the instrument either by clicking the X button from the detached window title bar or by double clicking the tool name from the tool menu. The minimize and maximize buttons are also available on the detached window title bar and should work as expected. When reattaching the instrument, the reattached instrument will be the one currently selected. + +**Preconditions:** + - Scopy is installed on the system. + - Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS. + - Use :ref:`pluto-usb-instrument-detaching ` setup. + +**Steps:** + 1. Click on the connected Pluto device and connect to it. Select the 'ADC - Time' plugin. + 2. Double click the 'ADC - Time' tool name from the tool menu. + - **Expected Result:** The 'ADC - Time' instrument should be detached from the main window. The title bar of the detached window should include the name of the detached instrument. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 3. Click the square button from the tool menu to start the ADC data aquisition. + - **Expected Result:** The ADC should start acquiring data. The data should be displayed in the detached window. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + + 4. Click the X button from the detached window title bar. + - **Expected Result:** The 'ADC - Time' instrument should be reattached to the main window. The 'ADC - Time' instrument should be the one currently selected. + - **Actual result:** As expected + +.. + Actual test result goes here. +.. + +**Tested OS:** Windows 10, macOS 14.5 + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS + +.. + The result of the test goes here (PASS/FAIL). + diff --git a/testing_results/testing_results_v2.0.0/index.rst b/testing_results/testing_results_v2.0.0/index.rst new file mode 100644 index 0000000000..2fbc88e10d --- /dev/null +++ b/testing_results/testing_results_v2.0.0/index.rst @@ -0,0 +1,20 @@ +.. _tests_scopy: + +Test Cases +=============================================================================== + +Current reports +------------------------ + +.. include:: test_report.rst + +Contents +--------------------------------------------------------------------- + +.. toctree:: + :includehidden: + :maxdepth: 3 + + testing_guide + plugins/index + general/index diff --git a/testing_results/testing_results_v2.0.0/plugins/adc/adc_tests.rst b/testing_results/testing_results_v2.0.0/plugins/adc/adc_tests.rst new file mode 100644 index 0000000000..88038e6021 --- /dev/null +++ b/testing_results/testing_results_v2.0.0/plugins/adc/adc_tests.rst @@ -0,0 +1,1511 @@ +.. _adc_tests: + +ADC Plugin - Test Suite +======================= + +.. note:: + + User guide: :ref:`ADC user guide` + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - + - + - + - + - + +Setup environment +------------------ + +.. _adalm-pluto_device_usb: + +**Pluto.usb:** + - Connect a pluto device via usb to your PC + - connect to the device in Scopy with ADCPlugin enabled + +.. _adalm-pluto_device_emu: + +**Pluto.emu:** + - Press the add device button and go to emulator + - Select pluto device + - Enable, verify and select all plugins available + - Connect to the device + +.. _adalm-pluto_device_siggen: + +**Pluto.signalGenerator:** + - Requires DAC and Debugger tests to work + - Go to Debugger, select context0/ad9361-phy/TX_LO/frequency and set it to 2400000000. + Do the same for context0/ad9361-phy/RX_LO/frequency + - Go to DAC plugin, mode: DDS, dds mode: independent I/Q control. + TX1_I_F1 scale: -40, TX1_I_F2: -40, TX1_Q_F1: -30, TX1_Q_F2: -30. set all frequency values to 1MHz. + - Run DAC plugin. + + +.. _adc_time_tests: + +ADC-Time +-------- + +Test 1 - X-AXIS +^^^^^^^^^^^^^^^ + +.. _TST.ADC_TIME.X_AXIS: + +**UID:** TST.ADC_TIME.X_AXIS + +**Description:** Verify X-axis behavior under different configurations + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Scroll down and turn on plot labels in the settings panel + 2. Set XMode to Samples on the X-axis + 3. Set buffer size to 100 + 4. Press Single + - **Expected result:** Plot labels should go up to 100, and channel curves + should span across the whole plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Turn off Sync buffer-plot sizes + 6. Set plot size to 200 + 7. Press Single + - **Expected result:** Plot labels should go up to 200, and channel curves should span across the whole plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + 8. Turn on Rolling mode + - **Expected result:** Plot labels should invert, going from 200 to 0 + - **Actual result:** + +.. + Actual test result goes here. +.. + + 9. Change XMin to 200 and XMax to -100 + 10. Press Single + - **Expected result:** Plot labels should range from 300 to -100, with channel curves centered and between samples 200 and 0 + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 2 - Y-AXIS +^^^^^^^^^^^^^^^ +.. _TST.ADC_TIME.Y_AXIS: + +**UID:** TST.ADC_TIME.Y_AXIS + +**Description:** Verify Y-axis behavior under different configurations + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Scroll down and turn on plot labels in the settings panel + 2. Turn on Autoscale and press Run + - **Expected result:** Y-axis should automatically scale according to channel curves + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Press Stop + 4. Turn Autoscale off + 5. Set YMode to ADC Counts + 6. Set Min to -4000 and Max to 4000 + 7. Press Single + - **Expected result:** Y-axis labels should range from -4000 to 4000, and curves should vertically adjust accordingly + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 3 - XY PLOT +^^^^^^^^^^^^^^^^ + +.. _TST.ADC_TIME.XY_PLOT: + +**UID:** TST.ADC_TIME.XY_PLOT + +**Description:** Verify XY plot functionality and visualization + +**Preconditions:** + - :ref:`Pluto.usb` + - :ref:`Pluto.signalGenerator` + - OS: ANY + +**Steps:** + 1. Run Pluto.signalGenerator setup + 2. Turn on XY PLOT + - **Expected result:** A new plot should appear on the right + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Turn on Autoscale + - **Expected result:** On the time plot, both channel curves should + look the same, but voltage0 should have a higher amplitude + - **Actual result:** + +.. + Actual test result goes here. +.. + + 4. Set X Axis source to voltage0 + - **Expected result:** A small circular curve should appear on the XY plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Set X Axis source to voltage1 + - **Expected result:** A larger circular curve should appear on the XY plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + 6. Turn Plot X source on and off + - **Expected result:** A line cutting the circle should be visible in a different color + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 4 - Settings +^^^^^^^^^^^^^^^^^ + +.. _TST.ADC_TIME.SETTINGS: + +**UID:** TST.ADC_TIME.SETTINGS + +**Description:** Change Plot Title and toggle various plot settings + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Change Plot Title to "test" + - **Expected result:** text in top left should change to "test" + - **Actual result:** + +.. + Actual test result goes here. +.. + + 2. Turn on and off plot labels + - **Expected result:** labels on x and y axis should appear + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Change thickness and style to all available modes and observe the changes + - **Expected result:** channel curves' appearance should behave as expected + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 5 - Print +^^^^^^^^^^^^^^ + +.. _TST.ADC_TIME.PRINT: + +**UID:** TST.ADC_TIME.PRINT + +**Description:** Save the plot as a PDF file via the print functionality + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Run :ref:`Pluto.signalGenerator` setup + 2. Press the single button + 3. Press the print button + 4. Select a folder and save the file + - **Expected result:** a new PDF file should appear within the folder containing + the last view of the plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 6 - Info +^^^^^^^^^^^^^ + +.. _TST.ADC_TIME.INFO: + +**UID:** TST.ADC_TIME.INFO + +**Description:** Open the ADC plugin documentation via the info button + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Press the info button in the top left corner of the window + - **Expected result:** this should open the ADC plugin documentation. + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 7 - Plot Navigation +^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.PLOT_NAVIGATION: + +**UID:** TST.PLOT_NAVIGATION + +**Description:** Test plot zooming, panning, and undo features + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Scroll down and turn on plot labels in the settings panel + 2. Place mouse cursor within the plot and use the scroll wheel + - **Expected result:** should zoom in/out on the area at the cursor, should not be able to zoom out more than the default view + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Right-click the plot after zooming in + - **Expected result:** should undo the zoom + - **Actual result:** + +.. + Actual test result goes here. +.. + + 4. Select an area on the plot using left-click + - **Expected result:** should zoom in exactly on the selected area + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Zoom in using the selection method, then hold left shift button and zoom using the scroll wheel + - **Expected result:** should pan left and right + - **Actual result:** + +.. + Actual test result goes here. +.. + + 6. Zoom in using all methods described above and press right-click until zoom is back to default + - **Expected result:** should undo each zoom operation one by one + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 8 - ADC-Time Channel Settings +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.ADC_TIME_CHANNEL_SETTINGS: + +**UID:** TST.ADC_TIME_CHANNEL_SETTINGS + +**Description:** Test Y-axis settings and adjustments for the ADC-Time tool + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Double-click on the voltage0 channel and go to the right menu which pops up + 2. Enable Y-AXIS and move up and down the axis handle + - **Expected result:** this should move the channel curve within the Y-axis + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Turn autoscale off. Set YMode to ADC Counts, Min to -4000 and Max to 4000, and press single + - **Expected result:** only voltage0 curve should vertically adjust + - **Actual result:** + +.. + Actual test result goes here. +.. + + 4. Turn off Y-AXIS + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 9 - Measure +^^^^^^^^^^^^^^^^ + +.. _TST.MEASURE: + +**UID:** TST.MEASURE + +**Description:** Test the Measure functionality, enabling panels +and checking frequency and stats + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Double-click on the voltage0 channel and go to the right menu which pops up + 2. Open the Measure menu at the bottom of the window, enable Measure Panel and Stats panel + - **Expected result:** check frequency measure and stats in the horizontal measurements table, + middle measure and stats in the vertical measurements table. Frequency should be around 1MHz in + both panels, middle should be hovering around the 0 value in both panels + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Open the Measure menu and show all Stats and Measurements + - **Expected result:** all checkboxes in the measurement tables should be checked and each + should have a corresponding label above and below the plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + 4. Turn off measurements + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 10 - Cursors +^^^^^^^^^^^^^^^^^ + +.. _TST.CURSORS: + +**UID:** TST.CURSORS + +**Description:** Test cursor functionality including synchronization, +tracking, and moving readouts + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Double-click on the voltage0 channel and go to the right menu which pops up + 2. Run :ref:`Pluto.signalGenerator` setup + 3. In ADC, set X-AXIS buffer size to 200, XMode to Sample, and TMode to ADC Counts + 4. Open the Cursors menu at the bottom of the window. Enable X and Enable Y + 5. Move the X cursors on the plot via the axis handles and place one on voltage0 sine high peak and the other on the next low peak + - **Expected result:** delta x should be around 15 samples between voltage0 high peak and low peak + - **Actual result:** + +.. + Actual test result goes here. +.. + + 6. Lock X cursors via the Cursor menu. Move one cursor to a voltage1 high peak + - **Expected result:** the second cursor should move and maintain the same delta. High peak to low peak should match in both voltage0 and voltage1 + - **Actual result:** + +.. + Actual test result goes here. +.. + + 7. Enable track and select voltage0 + - **Expected result:** markers should appear on the voltage0 curve synced with the X cursor. Values in cursor readouts should change accordingly + - **Actual result:** + +.. + Actual test result goes here. +.. + + 8. Select voltage1 channel + - **Expected result:** markers and readouts should now be related to voltage1 + - **Actual result:** + +.. + Actual test result goes here. +.. + + 9. Turn off track and measure voltage0 and voltage1 amplitudes + - **Expected result:** for voltage0 delta y should be around 1.4kV and for voltage1 500V + - **Actual result:** + +.. + Actual test result goes here. +.. + + 10. Enable move readouts. Click and hold the readouts to move them + - **Expected result:** should be able to move the readouts anywhere within the plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +.. _adc_frequency_tests: + +ADC-Frequency +------------- + +Test 1 - X-Axis settings +^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.ADC_FREQ.X_AXIS_SETTINGS: + +**UID:** TST.ADC_FREQ.X_AXIS_SETTINGS + +**Description:** Adjust X-axis settings for frequency and sample-based +plotting in the ADC plugin + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Scroll down and turn on plot labels in the settings panel + 2. Set XMode to Samples, buffer size to 4000, and press single + - **Expected result:** Plot labels should go up to 4000, and channel curves should span across the whole plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Set XMode to Frequency, XMin to 0.5 MHz, XMax to 2 MHz, and press single + - **Expected result:** Plot labels should be from 0.5 MHz to 2 MHz, and channel curves should be centered + - **Actual result:** + +.. + Actual test result goes here. +.. + + 4. Set frequency offset to 1 MHz and press single + - **Expected result:** Curves should move 1 MHz to the left + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 2 - Y-Axis settings +^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.ADC_FREQ.Y_AXIS_SETTINGS: + +**UID:** TST.ADC_FREQ.Y_AXIS_SETTINGS + +**Description:** Adjust Y-axis settings, including autoscaling and manual +range settings + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Scroll down and turn on plot labels in the settings panel + 2. Turn on autoscale and press run + - **Expected result:** Y-axis should automatically scale according to the channel curves + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Press stop, turn autoscale off, set YMode to ADC Counts, Min to -140, Max to 20, and press single + - **Expected result:** Y-axis labels should be from -140 to 20, and curves should vertically adjust + - **Actual result:** + +.. + Actual test result goes here. +.. + + 4. Set power offset to 20 dB and press single + - **Expected result:** Curves should move 20 dB up + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Press run and change through all the window options and window correction + - **Expected result:** The curves should change slightly in real time + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 3 - Settings adjustment +^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.ADC_FREQ.SETTINGS_ADJUSTMENT: + +**UID:** TST.ADC_FREQ.SETTINGS_ADJUSTMENT + +**Description:** Adjust plot settings such as title, labels, thickness, +and style + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Change Plot Title to "test" + - **Expected result:** Text in the top left should change to "test" + - **Actual result:** + +.. + Actual test result goes here. +.. + + 2. Turn on and off plot labels + - **Expected result:** Labels on X and Y axis should appear + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Change thickness and style to all available modes and observe the changes + - **Expected result:** Channel curves should adjust appearance as expected + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 4 - Print plot +^^^^^^^^^^^^^^^^^^^ + +.. _TST.ADC_FREQ.PRINT_PLOT: + +**UID:** TST.ADC_FREQ.PRINT_PLOT + +**Description:** Print the current plot to a PDF file + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Run :ref:`Pluto.signalGenerator` setup + 2. Press the single button and then the print button + 3. Select a folder and save the file + - **Expected result:** A new PDF file should appear in the folder containing the last view of the plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 5 - View plugin documentation +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.ADC_FREQ.VIEW_PLUGIN_DOC: + +**UID:** TST.ADC_FREQ.VIEW_PLUGIN_DOC + +**Description:** Open the ADC plugin documentation + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Press the info button in the top left corner of the window + - **Expected result:** The ADC plugin documentation should open + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 6 - Y-Axis channel settings +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.ADC_FREQ.Y_AXIS_CHANNEL_SETTINGS: + +**UID:** TST.ADC_FREQ.Y_AXIS_CHANNEL_SETTINGS + +**Description:** Adjust the Y-axis for individual channel curve manipulation + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Enable Y-Axis and move the axis handle up and down + - **Expected result:** The channel curve should move within the Y-axis + - **Actual result:** + +.. + Actual test result goes here. +.. + + 2. Turn off autoscale, set YMode to ADC Counts, Min to -140, Max to 20, and press single + - **Expected result:** Only the voltage0 curve should vertically adjust + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Turn off Y-Axis + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 7 - Marker settings +^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.ADC_FREQ.MARKER_SETTINGS: + +**UID:** TST.ADC_FREQ.MARKER_SETTINGS + +**Description:** Use markers to identify peaks on channel curves + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Run :ref:`Pluto.signalGenerator` setup + 2. Press run and enable the marker + 3. Set marker type to peak and count to 5 + - **Expected result:** 5 markers should appear on voltage0's curve at the highest peaks + - **Actual result:** + +.. + Actual test result goes here. +.. + + 4. Repeat the process with a count of 7 + - **Expected result:** 7 markers should appear on voltage0's curve at the highest peaks + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Check the table below the plot in peak mode + - **Expected result:** The highest peak should be at 1 MHz + - **Actual result:** + +.. + Actual test result goes here. +.. + + 6. Set marker type to fixed and count to 5 + - **Expected result:** 5 movable cursors should appear + - **Actual result:** + +.. + Actual test result goes here. +.. + + 7. Repeat for a count of 7 + - **Expected result:** 7 movable cursors should appear + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 8 - Cursor settings +^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.ADC_FREQ.CURSOR_SETTINGS: + +**UID:** TST.ADC_FREQ.CURSOR_SETTINGS + +**Description:** Use cursors to measure specific points on channel curves. + +**Preconditions:** + - :ref:`Pluto.usb` + - OS: ANY + +**Steps:** + 1. Run :ref:`Pluto.signalGenerator` setup + 2. Press run and set X-Axis buffer size to 200, XMode to Sample, and TMode to ADC Counts + 3. Open the Cursors menu and enable X and Y cursors + 4. Move the X cursor on the plot and place one on voltage0's highest peak + - **Expected result:** The cursor should measure 1 MHz in the readouts + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Enable track and select voltage0 + - **Expected result:** Markers should appear on the voltage0 curve, synced with the X cursor + - **Actual result:** + +.. + Actual test result goes here. +.. + + 6. Select voltage1 channel + - **Expected result:** Markers and readouts should now be related to voltage1 + - **Actual result:** + +.. + Actual test result goes here. +.. + + 7. Turn off track and measure voltage0's highest peak using the Y cursor + - **Expected result:** The cursor should measure about -13 dB in the readouts + - **Actual result:** + +.. + Actual test result goes here. +.. + + 8. Enable move readouts and click and hold the readouts to move them + - **Expected result:** Readouts should be movable within the plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +.. _adc_preferences_tests: + +Preferences +----------- + +Test 1 - X Scale Position +^^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.PREF.X_SCALE_POS: + +**UID:** TST.PREF.X_SCALE_POS + +**Description:** Change the X-axis scale position and verify the label's position on the plot + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Change Plot X-Axis scale position to Top, restart app, open ADC-Time and enable plot labels in SETTINGS panel + - **Expected result:** Axis labels should appear on top + - **Actual result:** + +.. + Actual test result goes here. +.. + + 2. Do this again for Bottom option + - **Expected result:** Axis labels should appear on the bottom + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Repeat for ADC-Frequency + - **Expected result:** Same result for ADC-Frequency + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 2 - Y Scale Position +^^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.PREF.Y_SCALE_POS: + +**UID:** TST.PREF.Y_SCALE_POS + +**Description:** Change the Y-axis scale position and verify the label's +position on the plot + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Change Plot Y-Axis scale position to Right, restart app, open ADC-Time and enable plot labels in SETTINGS panel + - **Expected result:** Axis labels should appear on the right + - **Actual result:** + +.. + Actual test result goes here. +.. + + 2. Do this again for Left option + - **Expected result:** Axis labels should appear on the left + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Repeat for ADC-Frequency + - **Expected result:** Same result for ADC-Frequency + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 3 - Channel Handle Position +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.PREF.CH_HANDLE_POS: + +**UID:** TST.PREF.CH_HANDLE_POS + +**Description:** Change the Y-handle position and verify the appearance of the handle + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Change Plot channel Y-handle position to Right, restart app, open + ADC-Time, double click voltage0 to open channel settings and enable Y-AXIS + + - **Expected result:** Axis handle should appear on the right + - **Actual result:** + +.. + Actual test result goes here. +.. + + 2. Do this again for Left option + - **Expected result:** Axis handle should appear on the left + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Repeat for ADC-Frequency + - **Expected result:** Same result for ADC-Frequency + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 4 - X Cursor Position +^^^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.PREF.X_CURSOR_POS: + +**UID:** TST.PREF.X_CURSOR_POS + +**Description:** Change the X-cursor position and verify the cursor's appearance. + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Change Plot X-Cursor position to Top, restart app, open ADC-Time and enable x cursors + - **Expected result:** X cursor handle should appear on top + - **Actual result:** + +.. + Actual test result goes here. +.. + + 2. Do this again for Bottom option + - **Expected result:** X cursor handle should appear on the bottom + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Repeat for ADC-Frequency + - **Expected result:** Same result for ADC-Frequency + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 5 - Y Cursor Position +^^^^^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.PREF.Y_CURSOR_POS: + +**UID:** TST.PREF.Y_CURSOR_POS + +**Description:** Change the Y-cursor position and verify the cursor's appearance + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Change Plot Y-Cursor position to Right, restart app, open ADC-Time and enable y cursors + - **Expected result:** Y cursor handle should appear on the right + - **Actual result:** + +.. + Actual test result goes here. +.. + + 2. Do this again for Left option + - **Expected result:** Y cursor handle should appear on the left + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Repeat for ADC-Frequency + - **Expected result:** Same result for ADC-Frequency + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 6 - Show Buffer +^^^^^^^^^^^^^^^^^^^^ + +.. _TST.PREF.SHOW_BUFFER: + +**UID:** TST.PREF.SHOW_BUFFER + +**Description:** Enable/disable the buffer and verify its appearance on the plot + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Set buffer to disabled, open ADC-Time + - **Expected result:** There should be no buffer previewer above the plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + 2. Do this again for the enabled option + - **Expected result:** Buffer previewer should appear above the plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 7 - Default YMode +^^^^^^^^^^^^^^^^^^^^^^ + +.. _TST.PREF.DEFAULT_YMODE: + +**UID:** TST.PREF.DEFAULT_YMODE + +**Description:** Set the default Y-mode and verify its behavior in ADC-Time + +**Test prerequisites:** + - Emulator tests + +**Preconditions:** + - :ref:`Pluto.emu` + - OS: ANY + +**Steps:** + 1. Set YMode to % Full scale, restart app, open ADC-Time + - **Expected result:** In Y-AXIS, YMODE should be % Full scale + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). diff --git a/testing_results/testing_results_v2.0.0/plugins/adc/index.rst b/testing_results/testing_results_v2.0.0/plugins/adc/index.rst new file mode 100644 index 0000000000..567f62fdf8 --- /dev/null +++ b/testing_results/testing_results_v2.0.0/plugins/adc/index.rst @@ -0,0 +1,13 @@ +.. _tests_adc: + +ADC +=============================================================================== + +Contents +--------------------------------------------------------------------- + +.. toctree:: + :includehidden: + :maxdepth: 3 + + adc_tests diff --git a/testing_results/testing_results_v2.0.0/plugins/dac/dac_tests.rst b/testing_results/testing_results_v2.0.0/plugins/dac/dac_tests.rst new file mode 100644 index 0000000000..e2393c1e73 --- /dev/null +++ b/testing_results/testing_results_v2.0.0/plugins/dac/dac_tests.rst @@ -0,0 +1,764 @@ +.. _dac_tests: + +DAC Plugin - Test suite +======================= + +.. note:: + + User guide: :ref:`DAC Plugin user Guide` + +The DAC plugin tests are a set of tests that are run to verify the DAC plugin in Scopy. + +The following apply for all the test cases in this suite. +If the test case has special requirements, they will be listed in the test case section. + + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - + - + - + - + - + +Setup environment: +------------------- + +.. _adalm_pluto_emu_setup: + +**AdalmPluto.Emu:** + - Open Scopy. + - Start the IIO-EMU process. + - Connect to the ADALM-Pluto device using the EMU dropdown. + +.. _adalm_pluto_device_setup: + +**AdalmPluto.Device:** + - Open Scopy. + - Connect the ADALM-Pluto device to the system. + - Connect to the ADALM-Pluto device in Scopy using USB/network backend. + +**Depends on::** + - Test TST.PREFS.RESET + +Prerequisites: + - Scopy v2.0.0 or later with DAC plugin installed on the system. + - Tests listed as dependencies are successfully completed. + - Reset .ini files to default using the Preferences "Reset" button. + +Test 1 - Compatibility with device +---------------------------------------------------- + +.. _TST.DAC.COMPAT: + +**UID:** TST.DAC.COMPAT + +**Description:** This test verifies that the DAC plugin is compatible with the selected device +and that the plugin is able to correctly parse it. + +**Preconditions:** + - :ref:`AdalmPluto.Emu` + - OS: ALL (Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS) + +**Steps:** + 1. Open the DAC plugin. + 2. Switch the "Mode" to "Buffer" and check the "Channels" list: + - **Expected result:** The channels list contains the following: **cf-ad9361-dds-core-lpc:voltage0** + and **cf-ad9361-dds-core-lpc:voltage1**. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Switch the "Mode" to "DDS" and check the TX section: + - **Expected result:** The TX section contains one entry with "TX1". + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 2 - Buffer mode file loading +---------------------------------------------------- + +.. _TST.DAC.BUFFER_LOAD: + +**UID:** TST.DAC.BUFFER_LOAD + +**Description:** This test verifies that the DAC plugin is able to load a file in buffer mode. + +**Preconditions:** + - :ref:`AdalmPluto.Emu` + - OS: ALL (Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS) + +**Resources:** + - ``__ + - ``__ + +**Steps:** + 1. Open the DAC plugin. + 2. Switch the "Mode" to "Buffer". + 3. Select the *sine_complex_1_15360_sr_15360000_samps_40000_ampl_32767.csv* file using the + "Browse" button. + 4. Press the "Load" button. + - **Expected result:** + - The file should be loaded successfully. + - The "File Size" field is populated with ** 40 ksamples**. + - The Run button is enabled. + - A new section called "DATA CONFIGURATION" should appear. + - The bottom log section contains the following entry structure: *[timestamp] + Successfully loaded: [file name]*. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Select the *tutorial_chapters.json* file from the resources provided above + using the "Browse" button. + 6. Press the "Load" button. + - **Expected result:** + - The file should NOT be loaded. + - The Run button is disabled. + - The bottom log section contains the following entry structure: *[timestamp] + Failed to load: [file name]*. + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 3 - Buffer mode channel selection +---------------------------------------------------- + +.. _TST.DAC.BUFFER_CHANNEL_SELECT: + +**UID:** TST.DAC.BUFFER_CHANNEL_SELECT + +**Description:** This test verifies that the DAC plugin is able to validate channel selection in buffer mode. + +**Preconditions:** + - :ref:`AdalmPluto.Device` + - OS: ANY + +**Resources:** + - ``__ + +**Steps:** + 1. Open the DAC plugin. + 2. Switch the "Mode" to "Buffer". + 3. Select the *sine_complex_1_15360_sr_15360000_samps_40000_ampl_32767.csv* file using the + "Browse" button. + 4. Press the "Load" button. + 5. Check the channels list for enabled channels: + - **Expected result:** Both channels are enabled. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 6. Press "Run". + - **Expected result:** + - The "Run" button changes to "Stop". + - The bottom log section contains the following entry structure: + *[timestamp] Pushed 40000 samples, 160000 bytes (1/1 buffers).* + - **Actual result:** + +.. + Actual test result goes here. +.. + + 7. While the plugin is running, disable one of the channels. + - **Expected result:** + - The plugin keeps running. + - The bottom log section contains the following entry structure: + *[timestamp] Pushed 40000 samples, 80000 bytes (1/1 buffers).* + - **Actual result:** + +.. + Actual test result goes here. +.. + + 8. While the plugin is still running, disable the other channel. + - **Expected result:** + - The plugin stops running and the button change back to "Run". + - The bottom log section contains the following entry structure: + *[timestamp] Unable to create buffer, no channel enabled.* + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 4 - Buffer mode file size validation +--------------------------------------------------------- + +.. _TST.DAC.BUFFER_FILE_SIZE: + +**UID:** TST.DAC.BUFFER_FILE_SIZE + +**Description:** This test verifies that the DAC plugin is able to validate the file +size in buffer mode. + +**Preconditions:** + - :ref:`AdalmPluto.Device` + - OS: ANY + +**Resources:** + - ``__ + +**Steps:** + 1. Open the DAC plugin. + 2. Switch the "Mode" to "Buffer". + 3. Select the *sine_complex_1_15360_sr_15360000_samps_40000_ampl_32767.csv* file using the + "Browse" button. + 4. Press the "Load" button. + 5. Check the "File Size" field. + - **Expected result:** The "File Size" field is populated with **40 ksamples**. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 6. Change the "File Size" field to a value higher than the actual file size (write 50 and press Enter). + - **Expected result:** The field value remains 40 ksamples since that's + the maximum number of samples in the file. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 7. Change the "File Size" field to a value lower than the actual file size (write 30 and press Enter). + - **Expected result:** The field value changes to 30 ksamples. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 8. Change the "File Size" using the "+" button. + - **Expected result:** The field value changes to the 31. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 9. Change the "File Size" using the "-" button. + - **Expected result:** The field value changes to the 30. + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 5 - Cyclic buffer mode +--------------------------------------------- + +.. _TST.DAC.BUFFER_CYCLIC: + +**UID:** TST.DAC.BUFFER_CYCLIC + +**Description:** This test verifies the DAC plugin buffer generation in cyclic mode. + +**Depends on::** + - Test TST.ADC.* + - Test TST.Debugger.* + +**Preconditions:** + - :ref:`AdalmPluto.Device` + - ADALM-Pluto with loopback cable between RX and TX. + - OS: ALL (Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS) + +**Resources:** + - ``__ + +**Steps:** + 1. Open the DAC plugin. + 2. Switch the "Mode" to "Buffer". + 3. Select the *sine_complex_1_15360_sr_15360000_samps_40000_ampl_32767.csv* file using the + "Browse" button. + 4. Press the "Load" button. + 5. Press "Run". + 6. Open the Debugger plugin. + 7. In the **ad9361-phy** device, set the **frequency** attribute for the **altvoltage1 TX_LO** + and **altvoltage0 RX_LO** channels to 2450000000. + 8. Open the ADC plugin. + 9. Change the Buffer Size to 4096. + 10. Press "Run". + 11. Check the ADC plugin for the generated signal. + - **Expected result:** A sinewave is seen on the ADC plot. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 12. Stop the DAC plugin while monitoring the ADC plot. + - **Expected result:** The sinewave no longer appears. + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 6 - DDS modes +---------------------------------- + +.. _TST.DAC.DDS_MODES: + +**UID:** TST.DAC.DDS_MODES + +**Description:** This test verifies the DAC plugin DDS modes. + +**Preconditions:** + - :ref:`AdalmPluto.Emu` + - OS: ANY + +**Steps:** + 1. Open the DAC plugin. + 2. Switch the "Mode" to "DDS". + 3. Change the "DDS Mode" to **One CW Tone**. + - **Expected result:** + - One configuration panel appears. + - The configuration panel contains the following fields: + - **frequency**: 9.279985 MHz + - **scale**: -Inf db + - **phase**: 90 + - the channel name: "Tone 1 - TX1_I_F1" + - **Actual result:** + +.. + Actual test result goes here. +.. + + 4. Change the "DDS Mode" to **Two CW Tones**. + - **Expected result:** + - Two configuration panels appear having the same fields as in the previous step. + - The second channel name: "Tone 2 - TX1_I_F2" + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Change the "DDS Mode" to **Independent I/Q Control**. + - **Expected result:** + - Four configuration panels appear having the same fields as in the previous step. + - The third channel name: "Tone 1 - TX1_Q_F1" + - The fourth channel name: "Tone 2 - TX1_Q_F2" + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 7 - DDS mode sinewave generation +------------------------------------------------------ + +.. _TST.DAC.DDS_SINEWAVE: + +**UID:** + TST.DAC.DDS_SINEWAVE + +**Description:** + This test verifies the DAC plugin DDS mode sinewave generation. + +**Depends on::** + - Test TST.DEBUGGER.* + - Test TST.ADC.* + +**Preconditions:** + - :ref:`AdalmPluto.Device` + - ADALM-Pluto with loopback cable between RX and TX. + - OS: ALL (Windows, Linux-x86_64, Linux-arm64, Linux-arm32, macOS) + +**Steps:** + 1. Open the DAC plugin. + 2. Switch the "Mode" to "DDS". + 3. Change the "DDS Mode" to **One CW Tone**. + 4. Change the "frequency" to 1 MHz. + 5. Change the "scale" to 0 db. + 6. Open the Debugger plugin. + 7. In the **ad9361-phy** device, set the **frequency** attribute for the **altvoltage1 TX_LO** and + **altvoltage0 RX_LO** channels to 2450000000. + 8. Open the ADC plugin. + 9. Enable all the Measurements. + 10. Press "Run". + 11. Check the plot for the generated sinewave. + - **Expected result:** + - A sinewave should be seen on the ADC plot. + - The measurements show a frequency of 1 MHz. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 12. In the DAC plugin change the "DDS Mode" to **Disabled**. + - **Expected result:** The sinewave no longer appears on the ADC plot. + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 8 - DDS mode attributes refresh +----------------------------------------------------- + +.. _TST.DAC.DDS_ATTRS: + +**UID:** TST.DAC.DDS_ATTRS + +**Description:** This test verifies the DAC plugin DDS mode attributes refresh. + +**Depends on::** + - Test TST.DEBUGGER.* + +**Preconditions:** + - :ref:`AdalmPluto.Emu` + - OS: ANY + +**Steps:** + 1. Open the DAC plugin. + 2. Switch the "Mode" to "DDS". + 3. Change the "DDS Mode" to **One CW Tone**. + 4. Change the "frequency" to 1 MHz. + 5. Open the Debugger plugin. + 6. In the **cf-ad9361-dds-core-lpc** device, set the **frequency** attribute + for the **altvoltage0 TX1_I_F1** to 2000000. + 7. Go to the DAC Plugin and click the refresh attributes button. + - **Expected result:** The frequency field is updated to 2 MHz. + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + + +Test 9 - Plugin tutorial +--------------------------------- + +.. _TST.DAC.TUTORIAL: + +**UID:** TST.DAC.TUTORIAL + +**Description:** This test verifies the DAC plugin tutorial. + +**Preconditions:** + - :ref:`AdalmPluto.Emu` + - OS: ANY + +**Steps:** + 1. Open the DAC plugin. + 2. Click the "Info" button. + - **Expected result:** A pop-up window with 2 buttons (Tutorial and Documentation) + should appear. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 3. Click the "Documentation" button. + - **Expected result:** The documentation page opens in the default browser. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 4. Click the "Tutorial" button. + - **Expected result:** + - The tutorial opens as a walkthrough in the plugin. + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 10 - Channel attributes +-------------------------------------------- + +.. _TST.DAC.CHANNEL_ATTRS: + +**UID:** TST.DAC.CHANNEL_ATTRS + +**Description:** This test verifies the DAC plugin channel attributes. + +**Preconditions:** + - :ref:`AdalmPluto.Emu` + - OS: ANY + +**Steps:** + 1. Open the DAC plugin. + 2. Switch the "Mode" to "Buffer". + 3. In the "Channels" panel click on the first channel "cf-ad9361-dds-core-lpc:voltage0". + - **Expected result:** The channel attributes are displayed in the right side menu. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 4. Change the **sampling_frequency** attribute to 38400000. + - **Expected result:** The attribute is updated successfully. + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +Test 11 - Repeat data option +-------------------------------------------- + +.. _TST.DAC.REPEAT_DATA: + +**UID:** TST.DAC.REPEAT_DATA + +**Description:** This test verifies the DAC plugin repeat data option. +The data sets loaded from the file should be repeated to fill in all the enabled +channels. + +**Preconditions:** + - :ref:`AdalmPluto.Device` + - Enable 2 TX channels on your Pluto device. + - OS: ANY + +**Resources:** + - ``__ + +**Steps:** + 1. Open the DAC plugin. + 2. Switch the "Mode" to "Buffer". + 3. Browse and select the *sinewave_0.9_2ch.csv* file. + 4. Press the "Load" button. + - **Expected result:** The first 2 channels are enabled. + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Enable the remaining 2 channels from the channel list. + 6. Set the **Repeat data** option to true and press **Run**. + - **Expected result:** The console log displays the following message: *Pushed 8444 samples, 67552 bytes (1/1 buffers).* + - **Actual result:** + +.. + Actual test result goes here. +.. + + 7. Set the **Repeat data** option to false and press **Run**. + - **Expected result:** The console log displays the following message: *Not enough data columns for all enabled channels.* + - **Actual result:** + +.. + Actual test result goes here. +.. + + 8. Leave the **Repeat data** as is, disable the last 2 channels and press **Run**: + - **Expected result:** The console log displays the following message: *Pushed 8444 samples, 33776 bytes (1/1 buffers).* + - **Actual result:** + +.. + Actual test result goes here. +.. + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + diff --git a/testing_results/testing_results_v2.0.0/plugins/dac/index.rst b/testing_results/testing_results_v2.0.0/plugins/dac/index.rst new file mode 100644 index 0000000000..de2d1ccc00 --- /dev/null +++ b/testing_results/testing_results_v2.0.0/plugins/dac/index.rst @@ -0,0 +1,13 @@ +.. _tests_dac: + +DAC +=============================================================================== + +Contents +--------------------------------------------------------------------- + +.. toctree:: + :includehidden: + :maxdepth: 3 + + dac_tests diff --git a/testing_results/testing_results_v2.0.0/plugins/datalogger/datalogger_tests.rst b/testing_results/testing_results_v2.0.0/plugins/datalogger/datalogger_tests.rst new file mode 100644 index 0000000000..f437a75726 --- /dev/null +++ b/testing_results/testing_results_v2.0.0/plugins/datalogger/datalogger_tests.rst @@ -0,0 +1,1804 @@ +.. _datalogger_tests: + +Datalogger Test Suite +================================================================================ + +.. note:: + + User guide :ref:`Data Logger user guide ` + +The following apply to all tests below, any special requirements will be mentioned. + +**Prerequisites:** + - Scopy v2.0.0 or later with Data Logger installed on the system + - Tests listed as dependencies are successfully completed + - Reset .ini files to default by pressing **Reset** button in Preferences + +.. note:: + .. list-table:: + :widths: 50 30 30 50 50 + :header-rows: 1 + + * - Tester + - Test Date + - Scopy version + - Plugin version (N/A if not applicable) + - Comments + * - + - + - + - + - + +Setup Environment +------------------ + +.. _datalogger_adalm_pluto_emu_setup: + +**AdalmPluto.Emu:** + - Open Scopy + - Start the iio-emu process using Pluto option from the dropdown + - Connect to the Pluto Device + +.. _datalogger_adalm_pluto_device_setup: + +**AdalmPluto.Device:** + - Open Scopy + - Connect to the Pluto Device using IP or USB + +.. _datalogger_m2k_emu_setup: + +**M2k.Emu:** + - Open Scopy + - Start the iio-emu process using ADALM2000 option from the dropdown + - Connect to the M2k Device + +.. _TST_DATALOGGER_ENABLE_DISABLE_DATA_LOGGER_CHANNEL: + +Test 1: Enable and Disable Data Logger Channel +------------------------------------------------ + +**UID:** TST.DATALOGGER.ENABLE_DISABLE_DATA_LOGGER_CHANNEL + +**Description:** Enable the channel and check if the channel is enabled + +**OS:** ANY + +**Preconditions:** + - Connect to :ref:`AdalmPluto.Emu ` or + :ref:`AdalmPluto.Device ` + +**Steps:** + 1. Open Data Logger plugin + 2. Using channel menu enable channel **voltage0** of **xadc** device + 3. Press **Run** button + 4. Wait for some data to be collected + - **Expected result:** Curve will be displayed on the plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + 5. Using channel menu disable channel **voltage0** of **xadc** device + - **Expected result:** Curve will be removed from the plot + - **Actual result:** + +.. + Actual test result goes here. +.. + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +.. _TST_DATALOGGER_RUN_STOP_DATA_LOGGING: + +Test 2: Run and Stop Data Logging +------------------------------------ + +**UID:** TST.DATALOGGER.RUN_STOP_DATA_LOGGING + +**Description:** Start the Data Logger and check if the data is being collected + +**OS:** ANY + +**Preconditions:** + - Connect to :ref:`AdalmPluto.Emu ` or + :ref:`AdalmPluto.Device ` + +**Prerequisites:** + - :ref:`Enable and Disable Data Logger Channel ` is passed + +**Steps:** + 1. Open Data Logger plugin + 2. Using channel menu enable channel **voltage0** of **xadc** device + 3. Press **Run** button + - **Expected result:** + - Data is being collected and displayed on the plot + - **Run** button is changed to **Stop** + - **Actual result:** + +.. + Actual test result goes here. +.. + + 4. Press **Stop** button + - **Expected result:** + - Data is no longer being collected and displayed on the plot + - **Stop** button is changed to **Run** + - **Actual result:** + +.. + Actual test result goes here. +.. + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +.. _TST_DATALOGGER_CLEAR_COLLECTED_DATA: + +Test 3: Clear Collected Data +------------------------------ + +**UID:** TST.DATALOGGER.CLEAR_COLLECTED_DATA + +**Description:** Clear the data and check if the data is removed from the plot + +**OS:** ANY + +**Preconditions:** + - Connect to :ref:`AdalmPluto.Emu ` or + :ref:`AdalmPluto.Device ` + +**Prerequisites:** + - :ref:`Run and Stop Data Logging ` is passed + +**Steps:** + 1. Open Data Logger plugin + 2. Using channel menu enable channel **voltage0** of **xadc** device + 3. Press **Run** button + 4. Wait for some data to be collected + 5. Press **Stop** button + 6. Press **Clear** button + - **Expected result:** Data is removed from the plot + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +.. _TST_DATALOGGER_CLEAR_DATA_WHILE_RUNNING: + +Test 4: Clear data while running +---------------------------------- + +**UID:** TST.DATALOGGER.CLEAR_DATA_WHILE_RUNNING + +**Description:** Clear the data while running and check if the data is removed from the plot + +**OS:** ANY + +**Preconditions:** + - Connect to :ref:`AdalmPluto.Emu ` or + :ref:`AdalmPluto.Device ` + +**Prerequisites:** + - :ref:`Run and Stop Data Logging ` is passed + +**Steps:** + 1. Open Data Logger plugin + 2. Using channel menu enable channel **voltage0** of **xadc** device + 3. Press **Run** button + 4. Wait for some data to be collected + 5. Press **Clear** button + - **Expected result:** + - Data is removed from the plot + - Buffer is cleared and the starting point is reset to "0" + - **Actual result:** + +.. + Actual test result goes here. +.. + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +.. _TST_DATALOGGER_CREATE_NEW_DATA_LOGGER_TOOL: + +Test 5: Create a New Data Logger Tool +--------------------------------------- + +**UID:** TST.DATALOGGER.CREATE_NEW_DATA_LOGGER_TOOL + +**Description:** Create a new tool and check if the new tool is created + +**OS:** ANY + +**Preconditions:** + - Connect to :ref:`AdalmPluto.Emu ` or + :ref:`AdalmPluto.Device ` + +**Steps:** + 1. Open Data Logger plugin + 2. Press **+** button + - **Expected result:** + - New tool is created + - We are moved to the new tool + - The new tool has **x** button next to **+** + + - **Actual result:** + +.. + Actual test result goes here. +.. + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +.. _TST_DATALOGGER_REMOVE_A_CREATED_TOOL: + +Test 6: Remove a Created Tool +--------------------------------- + +**UID:** TST.DATALOGGER.REMOVE_A_CREATED_TOOL + +**Description:** Remove the tool and check if the tool is removed + +**OS:** ANY + +**Preconditions:** + - Connect to :ref:`AdalmPluto.Emu ` or + :ref:`AdalmPluto.Device ` + +**Prerequisites:** + - :ref:`Create a New Data Logger Tool ` is passed + +**Steps:** + 1. Open Data Logger plugin + 2. Press **+** button + 3. Press **x** button next to **+** + - **Expected result:** Tool is removed + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +.. _TST_DATALOGGER_VERIFY_REMOVAL_DISABLED_FOR_DEFAULT_TOOL: + +Test 7: Verify Removal Disabled for Default Tool +-------------------------------------------------- + +**UID:** TST.DATALOGGER.VERIFY_REMOVAL_DISABLED_FOR_DEFAULT_TOOL + +**Description:** Check if the remove tool is disabled for the first tool + +**OS:** ANY + +**Preconditions:** + - Connect to :ref:`AdalmPluto.Emu ` or + :ref:`AdalmPluto.Device ` + +**Steps:** + 1. Open Data Logger plugin + 2. Press **+** button + - **Expected result:** A new tool where **x** button is available is created + - **Actual result:** + +.. + Actual test result goes here. +.. + + + 3. Open original Data Logger tool + - **Expected result:** No **x** button is available + - **Actual result:** + +.. + Actual test result goes here. +.. + + +**Tested OS:** + +.. + Details about the tested OS goes here. + +**Comments:** + +.. + Any comments about the test goes here. + +**Result:** PASS/FAIL + +.. + The result of the test goes here (PASS/FAIL). + + +.. _TST_DATALOGGER_PRINT_COLLECTED_DATA: + +Test 8: Print Collected Data +------------------------------ + +**UID:** TST.DATALOGGER.PRINT_COLLECTED_DATA + +**Description:** Print the data and check if the data is printed + +**OS:** ANY + +**Preconditions:** + - Connect to :ref:`AdalmPluto.Emu ` or + :ref:`AdalmPluto.Device ` + +**Prerequisites:** + - :ref:`Run and Stop Data Logging ` is passed + +**Steps:** + 1. Open Data Logger plugin + 2. Using channel menu enable channel **voltage0** of **xadc** device + 3. Press **Run** button + 4. Wait for some data to be collected + 5. Press **Print** button + 6. Choose directory where to save the file + - **Expected result:** + - Data is saved to a pdf file in the chosen directory + - The file name structure is "Sopy-Data-Logger--