Testing add RBP level for all current tests

docs/tests/general/core/add_dev_tests.rst

@@ -38,7 +38,9 @@ Test 1: Verifying the device scanning functionality.
 
 **UID:** TST.ADD.SCAN_ALL
 
-**Description:** This test checks that the device scan correctly detects and 
+**RBP:** P0
+
+**Description:** This test checks that the device scan correctly detects and
 lists available devices when initiated.
 
 **Preconditions:**
@@ -81,6 +83,8 @@ Test 2: Verifying the local device scanning functionality.
 
 **UID:** TST.ADD.SCAN_LOCAL
 
+**RBP:** P3
+
 **Description:** This test checks that the device scan correctly detects and 
 lists available local devices when initiated.
 
@@ -125,7 +129,9 @@ Test 3: Verifying the ip device scanning functionality.
 
 **UID:** TST.ADD.SCAN_IP
 
-**Description:** This test checks that the device scan correctly detects and 
+**RBP:** P0
+
+**Description:** This test checks that the device scan correctly detects and
 lists available ip devices when initiated.
 
 **Preconditions:**
@@ -169,7 +175,9 @@ Test 4: Verifying the usb device scanning functionality.
 
 **UID:** TST.ADD.SCAN_USB
 
-**Description:** This test checks that the device scan correctly detects and 
+**RBP:** P0
+
+**Description:** This test checks that the device scan correctly detects and
 lists available usb devices when initiated.
 
 **Preconditions:**
@@ -211,6 +219,8 @@ Test 5: Verifying the serial device scanning functionality.
 
 **UID:** TST.ADD.SCAN_SERIAL
 
+**RBP:** P3
+
 **Description:** This test checks that the device scan correctly detects and 
 lists available serial devices when initiated.
 
@@ -256,7 +266,9 @@ Test 6: Scanning with no device.
 
 **UID:** TST.ADD.SCAN_EMPTY
 
-**Description:** This test checks whether an appropriate message is displayed 
+**RBP:** P0
+
+**Description:** This test checks whether an appropriate message is displayed
 when no device is found.
 
 **Preconditions:**
@@ -299,6 +311,8 @@ Test 7: Device validation.
 
 **UID:** TST.ADD.VERIFY
 
+**RBP:** P0
+
 **Description:** This test verifies that the device validation works correctly.
 
 **Test prerequisites:**
@@ -342,6 +356,8 @@ Test 8: Verify the "BACK" button from compatible plugin page.
 
 **UID:** TST.ADD.PLUGINS_BACK
 
+**RBP:** P3
+
 **Description:** This test checks if the **BACK** button works correctly.
 
 **Test prerequisites:**
@@ -387,7 +403,9 @@ Test 9: Verify the "ADD DEVICE" button from compatible plugin page (single plugi
 
 **UID:** TST.ADD.PLUGINS_ADD_SINGLE
 
-**Description:** This test checks if the **ADD DEVICE** button works correctly. 
+**RBP:** P1
+
+**Description:** This test checks if the **ADD DEVICE** button works correctly.
 Only the main plugin of the device is used.
 
 **Test prerequisites:**
@@ -441,7 +459,9 @@ Test 10: Verify the "ADD DEVICE" button from compatible plugin page (multiple pl
 
 **UID:** TST.ADD.PLUGINS_ADD_MULTIPLE
 
-**Description:** This test checks if the **ADD DEVICE** button works correctly. 
+**RBP:** P1
+
+**Description:** This test checks if the **ADD DEVICE** button works correctly.
 Multiple plugins are used.
 
 **Test prerequisites:**
@@ -496,6 +516,8 @@ Test 11: Verify the "ADD DEVICE" button from compatible plugin page with no plug
 
 **UID:** TST.ADD.PLUGINS_EMPTY
 
+**RBP:** P1
+
 **Description:** This test checks if the **ADD DEVICE** button works correctly.
 
 **Test prerequisites:**

docs/tests/general/core/connection_tests.rst

@@ -48,6 +48,8 @@ Test 1: Verify the connection flow.
 
 **UID:** TST.CONN.SUCC
 
+**RBP:** P0
+
 **Description:** This test checks if the **Connect** button works correctly.
 
 **Test prerequisites:** 
@@ -94,7 +96,9 @@ 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 
+**RBP:** P0
+
+**Description:** This test verifies Scopy's behavior when the device is
 unplugged during the connection process.
 
 **Test prerequisites:** 
@@ -139,6 +143,8 @@ Test 3: Unplug the device while connecting (MANUAL-SCAN).
 
 **UID:** TST.CONN.UNPLUG_AUTO
 
+**RBP:** P3
+
 **Description:** This test verifies Scopy's behavior when the device is 
 unplugged during the connection process.
 
@@ -187,7 +193,9 @@ Test 4: Unplug the device before connecting.
 
 **UID:** TST.CONN.UNPLUG_BEFORE
 
-**Description:** This test verifies Scopy's behavior when the device is 
+**RBP:** P0
+
+**Description:** This test verifies Scopy's behavior when the device is
 unplugged before the connection process.
 
 **Test prerequisites:**
@@ -233,6 +241,8 @@ Test 5: Disconnecting a device.
 
 **UID:** TST.CONN.DISCONN
 
+**RBP:** P0
+
 **Description:** This test checks if the **Disconnect** button works correctly.
 
 **Test prerequisites:**

docs/tests/general/core/dev_tests.rst

@@ -46,7 +46,9 @@ Test 1: Verifying the device button.
 
 **UID:** TST.HP.DEV_BTN
 
-**Description:** To verify that clicking on the device button triggers the 
+**RBP:** P0
+
+**Description:** To verify that clicking on the device button triggers the
 expected action: displaying device details and device tools.
 
 **Test prerequisites:**
@@ -92,6 +94,8 @@ Test 2: Remove a device from device browser.
 
 **UID:** TST.DEV.FORGET
 
+**RBP:** P0
+
 **Description:** This test checks if the "Forget" (x) button work correctly.
 
 **Test prerequisites:**
@@ -133,6 +137,8 @@ Test 3: Remove a device from device browser while it is connected.
 
 **UID:** TST.DEV.FORGET_CONN
 
+**RBP:** P3
+
 **Description:** This test verifies whether Scopy properly handles the removal 
 of a connected device.
 
@@ -178,6 +184,8 @@ Test 4: Edit the name of the device.
 
 **UID:** TST.DEV.EDIT_NAME
 
+**RBP:** P3
+
 **Description:** This test checks if the **Edit pen** button work correctly.
 
 **Test prerequisites:**
@@ -225,6 +233,8 @@ Test 5: Select a tool.
 
 **UID:** TST.DEV.SELECT_TOOL
 
+**RBP:** P1
+
 **Description:** This test checks if the tool infrastructure works correctly.
 
 **Test prerequisites:**
@@ -279,6 +289,8 @@ Test 6: Detach a tool.
 
 **UID:** TST.DEV.DETACH_TOOL
 
+**RBP:** P3
+
 **Description:** This test checks if the tool detachment mechanism is working 
 correctly.
 
@@ -343,6 +355,8 @@ Test 7: Reopen the app with a detached tool.
 
 **UID:** TST.DEV.DETACH_TOOL_RE
 
+**RBP:** P3
+
 **Description:** This test checks whether detached tools retain their state upon 
 reconnection.
 
@@ -386,7 +400,9 @@ Test 8: Collapse device tools in the tool menu.
 
 **UID:** TST.DEV.COLLAPSE
 
-**Description:** This test verifies if the collapse feature works properly in 
+**RBP:** P1
+
+**Description:** This test verifies if the collapse feature works properly in
 the tool menu.
 
 **Test prerequisites:**
@@ -439,6 +455,8 @@ Test 9: Connecting to multiple devices.
 
 **UID:** TST.DEV.MULTI_CONN
 
+**RBP:** P1
+
 **Description:** This test checks if connecting to multiple devices is working 
 properly.
 
@@ -498,7 +516,9 @@ Test 10: Resource manager with multiple devices.
 
 **UID:** TST.DEV.RM_MULTI
 
-**Description:** This test verifies that the resource manager is being used 
+**RBP:** P1
+
+**Description:** This test verifies that the resource manager is being used
 properly.
 
 **Test prerequisites:**
@@ -555,7 +575,9 @@ Test 11: Devices order in device browser.
 
 **UID:** TST.DEV.ADD_ORDER
 
-**Description:** This test verifies that each newly added device is finally 
+**RBP:** P0
+
+**Description:** This test verifies that each newly added device is finally
 entered into the device browser.
 
 **Test prerequisites:**

docs/tests/general/core/emu_tests.rst

@@ -30,6 +30,8 @@ Test 1: Enable the emulator.
 
 **UID:** TST.EMU.EN
 
+**RBP:** P3
+
 **Description:** This test verifies if starting the emulator in Scopy works 
 correctly.
 
@@ -83,6 +85,8 @@ Test 2: EMU is not installed.
 
 **UID:** TST.EMU.NOT
 
+**RBP:** P3
+
 **Description:** This test verifies if Scopy handles the situation correctly 
 when the IIO emulator is not found.
 
@@ -126,6 +130,8 @@ Test 3: Disable the emulator.
 
 **UID:** TST.EMU.DIS
 
+**RBP:** P3
+
 **Description:** This test verifies if stopping the emulator in Scopy works 
 correctly.
 
@@ -174,6 +180,8 @@ Test 4: Disable the emulator while the emulated device is connected.
 
 **UID:** TST.EMU.DIS_CONN
 
+**RBP:** P3
+
 **Description:** The test verifies if Scopy handles the situation correctly 
 when an emulated device is connected and the "iio-emu" process is stopped.
 
@@ -224,6 +232,8 @@ Test 5: Verify adalm2000 emu device.
 
 **UID:** TST.EMU.EN_ADALM2000
 
+**RBP:** P3
+
 **Description:** This test verifies if starting the emulator in Scopy works 
 correctly (using adalm2000 device).
 
@@ -272,6 +282,8 @@ Test 6: Verify pluto emu device.
 
 **UID:** TST.EMU.EN_PLUTO
 
+**RBP:** P3
+
 **Description:** This test verifies if starting the emulator in Scopy works 
 correctly (using pluto device).
 
@@ -320,6 +332,8 @@ Test 7: Verify pqm emu device.
 
 **UID:** TST.EMU.EN_PQM
 
+**RBP:** P3
+
 **Description:** This test verifies if starting the emulator in Scopy works 
 correctly (using pqm device).
 
@@ -368,6 +382,8 @@ Test 8: Verify swiot_config emu device.
 
 **UID:** TST.EMU.EN_SWIOT_CONFIG
 
+**RBP:** P3
+
 **Description:** This test verifies if starting the emulator in Scopy works 
 correctly (using swiot_config device).
 
@@ -415,6 +431,8 @@ Test 9: Verify swiot_runtime emu device.
 
 **UID:** TST.EMU.EN_SWIOT_RUNTIME
 
+**RBP:** P3
+
 **Description:** This test verifies if starting the emulator in Scopy works 
 correctly (using swiot_runtime device).
 
@@ -463,6 +481,8 @@ Test 10: Verify generic emu device.
 
 **UID:** TST.EMU.EN_GENERIC
 
+**RBP:** P3
+
 **Description:** This test verifies if starting the emulator in Scopy works 
 correctly (using generic device).