PQM Tests

Rms tool

Note

User guide: Rms.

Note

Tester	Test Date	Scopy version	Plugin version (N/A if not applicable)	Comments

Setup environment:

PQM.Emu:

• Open Scopy.

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

• Run: python3 pqmDataWriter.py.

• Add the device in device browser.

• Connect to “ip:127.0.0.1”.

Test 1: Open Rms tool.

UID: TST.PQM.RMS_OPEN

RBP: P3

Description: This test verifies that the Rms tool opens correctly and is accessible without errors.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Rms tool.

2. Observe the application’s behavior.

   • Expected result: In the top section of the tool widget, there is an Info button, a PQEvents indicator, a Run button, a Single button, and a Settings button. The Settings menu is open, and the Settings button is in a checked state. In the center of the widget, there are two plots, each with labels positioned above them.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 2: Info button check.

UID: TST.PQM.RMS_INFO

RBP: P3

Description: This test verifies if the Info button works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Rms tool.

2. Click on the Info button.

   • Expected result: The RMS documentation page is opened in the browser.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 3: Single acquisition.

UID: TST.PQM.RMS_SINGLE

RBP: P3

Description: This test verifies if the single acquisition works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Rms tool.

2. Click on the Single button.

   • Expected result: Both the plot and the header labels are populated with values. A single block of data is acquired.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 4: Data acquisition.

UID: TST.PQM.RMS_RUN

RBP: P3

Description: This test verifies if the data acquisition works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Rms tool.

2. Click on the Start button.

   • Expected result: Both the plot and the header labels are populated with values. The data is updated every few seconds.

   • Actual result:

3. Click on the Stop button.

   • Expected result: The data acquisition stops.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 5: Settings button check.

UID: TST.PQM.RMS_SETTINGS

RBP: P3

Description: This test verifies if the Settings button works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Rms tool.

2. Click on the Settings button.

   • Expected result: The settings menu collapses and the button becomes unchecked.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 6: Data logging.

UID: TST.PQM.RMS_LOG

RBP: P3

Description: This test verifies if the logging mechanism works correctly.

Test prerequisites:

• TST.PQM.RMS_RUN.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Rms tool.

2. Make sure that the settings menu is open.

3. Make sure that data acquisition is stopped.

   • If data acquisition is running, the log section cannot be accessed.

4. Click on the LOG switch button.

   • Expected result: A browse section is displayed.

   • Actual result:

5. Click on the Browse button.

   • Expected result: A explorer window is displayed. Only directories can be selected.

   • Actual result:

6. Select a directory and click on the Open button.

   • Expected result: The explorer window is closed and the path to that directory is introduced in the browser section.

   • Actual result:

7. Click on the Run button.

   • Expected result: The LOG section remains open, but its elements can no longer be accessed and a .csv file is created in the selected directory.

   • Actual result:

8. Click on the Stop button.

   • Expected result: The LOG section can now be accessed, and the .csv file is populated with data.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 7: Data logging wrong path.

UID: TST.PQM.RMS_LOG_WRONG

RBP: P3

Description: This test verifies if the logging mechanism works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Rms tool.

2. Make sure that the settings menu is open.

3. Make sure that data acquisition is stopped.

   • If data acquisition is running, the log section cannot be accessed.

4. Click on the LOG switch button.

   • Expected result: A browse section is displayed.

   • Actual result:

5. Enter an invalid path in the line edit.

6. Click on the Run button.

   • Expected result: The LOG section get closed and no .csv file is created.

   • Actual result:

7. Click on the Stop button.

   • Expected result: The LOG section remains closed.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 8: PQEvents.

UID: TST.PQM.RMS_PQEVENTS

RBP: P3

Description: This test verifies if the PQEvents indicator works correctly.

Test prerequisites:

• TST.PQM.RMS_RUN.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Rms tool.

2. Click on the Run button.

3. Run iio_attr -u ip:127.0.0.1 -c pqm count0 countEvent 1 command.

   • Expected result: The PQEvents indicator becomes active.

   • Actual result:

4. Click on the Stop button.

   • Expected result: The PQEvents indicator is still active.

   • Actual result:

5. Click on the PQEvents indicator.

   • Expected result: The PQEvents indicator becomes inactive.

   • Actual result:

6. Run iio_attr -u ip:127.0.0.1 -c pqm count0 countEvent 0 command.

Tested OS:

Comments:

Result: PASS/FAIL

Test 9: PQEvents synchronization.

UID: TST.PQM.RMS_PQEVENTS_SYNC

RBP: P3

Description: This test verifies that the PQEvents indicator is synchronized between RMS and Harmonics tools. When the PQEvents button is reset in one tool, it must also be reset in the other tool.

Test prerequisites:

• TST.PQM.RMS_PQEVENTS.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Rms tool.

2. Click on the Run button.

3. Run iio_attr -u ip:127.0.0.1 -c pqm count0 countEvent 1 command.

   • Expected result: The PQEvents indicator becomes active.

   • Actual result:

4. Click on the Harmonics tool.

   • Expected result: The PQEvents indicator in the Harmonics tool is also active.

   • Actual result:

5. Click on the PQEvents indicator in the Harmonics tool.

   • Expected result: The PQEvents indicator becomes inactive.

   • Actual result:

6. Click on the Rms tool.

   • Expected result: The PQEvents indicator in the RMS tool is also inactive.

   • Actual result:

7. Click on the Stop button.

8. Run iio_attr -u ip:127.0.0.1 -c pqm count0 countEvent 0 command.

Tested OS:

Comments:

Result: PASS/FAIL

Harmonics tool

Note

User guide: Harmonics.

Note

Tester	Test Date	Scopy version	Plugin version (N/A if not applicable)	Comments

Setup environment:

PQM.Emu:

• Open Scopy.

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

• Run: python3 pqmDataWriter.py.

• Add the device in device browser.

• Connect to “ip:127.0.0.1”.

Test 1: Open Harmonics tool.

UID: TST.PQM.HARMONICS_OPEN

RBP: P3

Description: This test verifies that the Harmonics tool opens correctly and is accessible without errors.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Harmonics tool.

2. Observe the application’s behavior.

   • Expected result: In the top section of the tool widget, there is an Info button, a PQEvents indicator, a Run button, a Single button, and a Settings button. The Settings menu is open, and the Settings button is in a checked state. In the center, there are three components: THD, a table, and a plot.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 2: Info button check.

UID: TST.PQM.HARMONICS_INFO

RBP: P3

Description: This test verifies if the Info button works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Harmonics tool.

2. Click on the Info button.

   • Expected result: The Harmonics documentation page is opened in the browser.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 3: Single acquisition.

UID: TST.PQM.HARMONICS_SINGLE

RBP: P3

Description: This test verifies if the single acquisition works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Harmonics tool.

2. Click on the Single button.

   • Expected result: All the components are populated with values. The data in the table must be reflected on the plot. A single block of data is acquired.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 4: Data acquisition.

UID: TST.PQM.HARMONICS_RUN

RBP: P3

Description: This test verifies if the data acquisition works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Harmonics tool.

2. Click on the Start button.

   • Expected result: The data is updated every few seconds (only the values from the table and from the plot are updated). The data in the table must be reflected on the plot.

   • Actual result:

3. Click on the Stop button.

   • Expected result: The data acquisition stops.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 5: Overview plot features.

UID: TST.PQM.HARMONICS_OVERVIEW_PLOT

RBP: P3

Description: This test verifies that the overview plot works correctly. On the overview plot, the user can select which channel is displayed and which harmonic degrees to show by selecting cells from the table.

Test prerequisites:

• TST.PQM.HARMONICS_SINGLE.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Harmonics tool.

2. Open the settings menu and enable the Overview plot.

3. Click on the Single button.

   • Expected result: The table and overview plot are populated with data. The Ia row is highlighted and the corresponding values are drawn on the overview plot.

   • Actual result:

4. Click on the Ub row from the table.

   • Expected result: The entire row is selected and the Ub values are displayed on the overview plot. In the settings menu, the active channel is also Ub. Only one channel is visible at a time on the overview plot.

   • Actual result:

5. Select the first 6 values from row Ic (click on the first value and hold it down until you reach column 5).

   • Expected result: Only the respective values remain highlighted, and only the selected harmonic degrees (0 to 5) appear on the overview plot.

   • Actual result:

6. Compare the bar heights on the overview plot with the values in the selected cells.

   • Expected result: The bar heights on the overview plot match the numeric values displayed in the selected table cells.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 6: Settings button check.

UID: TST.PQM.HARMONICS_SETTINGS

RBP: P3

Description: This test verifies if the Settings button works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Harmonics tool.

2. Click on the Settings button.

   • Expected result: The settings menu collapses and the button becomes unchecked.

   • Actual result:

3. Click on the Settings button.

   • Expected result: The settings menu opens, and the button is checked. The menu contains two sections: General and Log. The General section contains Harmonics type (set to harmonics by default) and Active channel (set to Ia by default).

   • Actual result:

4. Select Ib from active channels dropdown.

   • Expected result: The Ib row from the table is highlighted (if the table is populated, then the plot data is changed accordingly).

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 7: Data logging.

UID: TST.PQM.HARMONICS_LOG

RBP: P3

Description: This test verifies if the logging mechanism works correctly.

Test prerequisites:

• TST.PQM.HARMONICS_RUN.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Make sure that the settings menu is open.

2. Make sure that data acquisition is stopped.

   • If data acquisition is running, the log section cannot be accessed.

3. Click on the LOG switch button.

   • Expected result: A browse section is displayed.

   • Actual result:

4. Click on the Browse button.

   • Expected result: An explorer window is displayed. Only directories can be selected.

   • Actual result:

5. Select a directory and click on the Open button.

   • Expected result: The explorer window is closed and the path to that directory is introduced in the browse section.

   • Actual result:

6. Click on the Run button.

   • Expected result: The LOG section remains open, but its elements can no longer be accessed and a .csv file is created in the selected directory.

   • Actual result:

7. Click on the Stop button.

   • Expected result: The LOG section can now be accessed, and the .csv file is populated with data.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 8: Data logging wrong path.

UID: TST.PQM.HARMONICS_LOG_WRONG

RBP: P3

Description: This test verifies if the logging mechanism works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Make sure that the settings menu is open.

2. Make sure that data acquisition is stopped.

   • If data acquisition is running, the log section cannot be accessed.

3. Click on the LOG switch button.

   • Expected result: A browse section is displayed.

   • Actual result:

4. Enter an invalid path in the line edit.

5. Click on the Run button.

   • Expected result: The LOG section is closed and no .csv file is created.

   • Actual result:

6. Click on the Stop button.

   • Expected result: The LOG section remains closed.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 9: PQEvents.

UID: TST.PQM.HARMONICS_PQEVENTS

RBP: P3

Description: This test verifies if the PQEvents indicator works correctly.

Test prerequisites:

• TST.PQM.HARMONICS_RUN.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Run button.

2. Run iio_attr -u ip:127.0.0.1 -c pqm count0 countEvent 1 command.

   • Expected result: The PQEvents indicator becomes active.

   • Actual result:

3. Click on the Stop button.

   • Expected result: The PQEvents indicator is still active.

   • Actual result:

4. Click on the PQEvents indicator.

   • Expected result: The PQEvents indicator becomes inactive.

   • Actual result:

5. Run iio_attr -u ip:127.0.0.1 -c pqm count0 countEvent 0 command.

Tested OS:

Comments:

Result: PASS/FAIL

Test 10: Current harmonics plots data correspondence.

UID: TST.PQM.HARMONICS_CURRENT_PLOTS_DATA

RBP: P3

Description: This test verifies that the data displayed on the individual current harmonics plots (Ia, Ib, Ic) corresponds with the data shown in the harmonics table. These plots display all harmonic values.

Test prerequisites:

• TST.PQM.HARMONICS_SINGLE.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Harmonics tool.

2. Click on the Single button.

   • Expected result: The table and the individual current harmonics plots (Ia, Ib, Ic) are populated with data.

   • Actual result:

3. Compare the values in the Ia row of the table with the bar heights on the Ia plot.

   • Expected result: All bars on the Ia plot correspond to the values in the Ia row. The bar heights match the numeric values displayed in the table cells.

   • Actual result:

4. Compare the values in the Ib row of the table with the bar heights on the Ib plot.

   • Expected result: All bars on the Ib plot correspond to the values in the Ib row. The bar heights match the numeric values displayed in the table cells.

   • Actual result:

5. Compare the values in the Ic row of the table with the bar heights on the Ic plot.

   • Expected result: All bars on the Ic plot correspond to the values in the Ic row. The bar heights match the numeric values displayed in the table cells.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Waveform tool

Note

User guide: Waveform.

Note

Tester	Test Date	Scopy version	Plugin version (N/A if not applicable)	Comments

Setup environment:

PQM.Emu:

• Open Scopy.

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

• Add the device in device browser.

• Connect to “ip:127.0.0.1”.

Test 1: Open Waveform tool.

UID: TST.PQM.WAVEFORM_OPEN

RBP: P3

Description: This test verifies that the Waveform tool opens correctly and is accessible without errors.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Waveform tool.

2. Observe the application’s behavior.

   • Expected result: In the top section of the tool widget, there is an Info button, a Run button, a Single button, and a Settings button. The Settings menu is open, and the Settings button is in a checked state. In the center, there are two plots.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 2: Info button check.

UID: TST.PQM.WAVEFORM_INFO

RBP: P3

Description: This test verifies if the Info button works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Waveform tool.

2. Click on the Info button.

   • Expected result: The Waveform documentation page is opened in the browser.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 3: Settings button check.

UID: TST.PQM.WAVEFORM_SETTINGS

RBP: P3

Description: This test verifies if the Settings button works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Waveform tool.

2. Click on the Settings button.

   • Expected result: The settings menu collapses and the button becomes unchecked.

   • Actual result:

3. Click on the Settings button.

   • Expected result: The settings menu opens, and the button is checked.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 4: Settings timespan check.

UID: TST.PQM.WAVEFORM_SETTINGS_TIMESPAN

RBP: P3

Description: This test verifies if the timespan spin box works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Waveform tool.

2. Make sure that the settings menu is open.

3. Click on (+) button.

   • Expected result: The timespan is increased and the x-axis range is now [-newValue, 0]. The maximum value must be 10.

   • Actual result:

4. Click on (-) button.

   • Expected result: The timespan is decreased and the x-axis range is now [-newValue, 0]. The minimum value must be 0.02.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 5: Settings rolling switch check.

UID: TST.PQM.WAVEFORM_SETTINGS_ROLLING

RBP: P3

Description: This test verifies if the rolling mode switch works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Waveform tool.

2. Make sure that the settings menu is open.

3. Enable Rolling mode swich.

   • Expected result: The switch is turned on, and the “triggered by” dropdown is inactive.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 6: Single acquisition triggered.

UID: TST.PQM.WAVEFORM_SINGLE_TRIG

RBP: P3

Description: This test verifies if the single acquisition works correctly (triggered mode).

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Waveform tool.

2. Make sure that the Rolling mode switch is turned off.

3. Click on the Single button.

   • Expected result: The curves are displayed on the plot in single shot format. A single block of data is acquired.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 7: Single acquisition rolling.

UID: TST.PQM.WAVEFORM_SINGLE_ROLL

RBP: P3

Description: This test verifies if the single acquisition works correctly (rolling mode).

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Waveform tool.

2. Make sure that the Rolling mode switch is turned on.

3. Click on the Single button.

   • Expected result: The curves are drawn from right to left until all the required samples for the plot are acquired. A single block of data is acquired.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 8: Data acquisition triggered.

UID: TST.PQM.WAVEFORM_RUN_TRIG

RBP: P3

Description: This test verifies if the data acquisition works correctly (triggered mode).

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Waveform tool.

2. Make sure that the Rolling mode switch is turned off.

3. Click on the Start button.

   • Expected result: The curves are displayed on the plot in single shot format. When new data is available, it is displayed on the screen.

   • Actual result:

4. Click on the Stop button.

   • Expected result: The data acquisition stops.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 9: Data acquisition rolling.

UID: TST.PQM.WAVEFORM_RUN_ROLL

RBP: P3

Description: This test verifies if the data acquisition works correctly (rolling mode).

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Waveform tool.

2. Make sure that the Rolling mode switch is turned on.

3. Click on the Start button.

   • Expected result: The curves are drawn from right to left until all the required samples for the plot are acquired. If there are non-zero values, a continuous motion illusion is created.

   • Actual result:

4. Click on the Stop button.

   • Expected result: The data acquisition stops.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 10: Plot zoom.

UID: TST.PQM.WAVEFORM_PLOT_ZOOM

RBP: P3

Description: This test verifies if, when zooming in on one plot, the x-axis range of the other plot is modified and matches the zoom range.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Waveform tool.

2. Zoom in on the first plot to a range smaller than the x-axis range.

   • Expected result: The x-axis range of the second plot is modified and matches the range of the first plot.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 11: Data logging.

UID: TST.PQM.WAVEFORM_LOG

RBP: P3

Description: This test verifies if the logging mechanism works correctly.

Test prerequisites:

• TST.PQM.WAVEFORM_RUN_ROLL.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Make sure that the settings menu is open.

2. Make sure that data acquisition is stopped.

   • If data acquisition is running, the log section cannot be accessed.

3. Click on the LOG switch button.

   • Expected result: A browse section is displayed.

   • Actual result:

4. Click on the Browse button.

   • Expected result: An explorer window is displayed. Only directories can be selected.

   • Actual result:

5. Select a directory and click on the Open button.

   • Expected result: The explorer window is closed and the path to that directory is introduced in the browser section.

   • Actual result:

6. Click on the Run button.

   • Expected result: The LOG section remains open, but its elements can no longer be accessed and a .csv file is created in the selected directory.

   • Actual result:

7. Click on the Stop button.

   • Expected result: The LOG section can now be accessed, and the .csv file is populated with data.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 12: Data logging wrong path.

UID: TST.PQM.WAVEFORM_LOG_WRONG

RBP: P3

Description: This test verifies if the logging mechanism works correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Make sure that the settings menu is open.

2. Make sure that data acquisition is stopped.

   • If data acquisition is running, the log section cannot be accessed.

3. Click on the LOG switch button.

   • Expected result: A browse section is displayed.

   • Actual result:

4. Enter an invalid path in the line edit.

5. Click on the Run button.

   • Expected result: The LOG section is closed and no .csv file is created.

   • Actual result:

6. Click on the Stop button.

   • Expected result: The LOG section remains closed.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 13: Concurrent acquisition with RMS and Harmonics.

UID: TST.PQM.WAVEFORM_CONCURRENT_ACQ

RBP: P3

Description: This test verifies that when RMS and Harmonics tools are running and the user starts acquisition on the Waveform tool, the acquisition on RMS and Harmonics stops automatically.

Test prerequisites:

• TST.PQM.RMS_RUN.

• TST.PQM.HARMONICS_RUN.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Rms tool.

2. Click on the Run button.

   • Expected result: Data acquisition starts on the RMS tool.

   • Actual result:

3. Click on the Harmonics tool.

4. Click on the Run button.

   • Expected result: Data acquisition starts on the Harmonics tool.

   • Actual result:

5. Click on the Waveform tool.

6. Click on the Run button.

   • Expected result: Data acquisition starts on the Waveform tool.

   • Actual result:

7. Click on the Rms tool.

   • Expected result: Data acquisition on the RMS tool has stopped. The Run button is no longer in the active/pressed state.

   • Actual result:

8. Click on the Harmonics tool.

   • Expected result: Data acquisition on the Harmonics tool has stopped. The Run button is no longer in the active/pressed state.

   • Actual result:

9. Click on the Waveform tool.

10. Click on the Stop button.

Tested OS:

Comments:

Result: PASS/FAIL

Settings tool

Note

User guide: Settings.

Note

Tester	Test Date	Scopy version	Plugin version (N/A if not applicable)	Comments

Setup environment:

PQM.Emu:

• Open Scopy.

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

• Add the device in device browser.

• Connect to “ip:127.0.0.1”.

Test 1: Open Settings tool.

UID: TST.PQM.SETTINGS_OPEN

RBP: P3

Description: This test verifies that the Settings tool opens correctly and is accessible without errors.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Settings tool.

2. Observe the application’s behavior.

   • Expected result: Three sections are displayed: System Time, Logging, and Config Values.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 2: Read config values.

UID: TST.PQM.SETTINGS_READ

RBP: P3

Description: This test verifies if the device attribute reading is done correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Settings tool.

2. Scroll down in the Config values section until you find the Read and Set buttons.

3. Click on the Read button.

   • Expected result: All fields in the section are populated.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL

Test 3: Write config values.

UID: TST.PQM.SETTINGS_WRITE

RBP: P3

Description: This test verifies if the device attribute writing is done correctly.

Test prerequisites:

• TST.CONN.SUCC.

Preconditions:

• Scopy is installed on the system.

• iio-emu is installed on the system.

• Use PQM.Emu setup.

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

Steps:

1. Click on the Settings tool.

2. Scroll down in the Config values section until you find the Read and Set buttons.

3. Click on the Read button.

   • Expected result: All fields in the section are populated.

   • Actual result:

4. Change the MsV Threshold value to 0.40.

5. Click on the Write button.

6. Click on the Read button.

   • Expected result: The MsV Threshold attribute value must be 0.40.

   • Actual result:

Tested OS:

Comments:

Result: PASS/FAIL