tests: general test cases fixes

Signed-off-by: Andrei Popa <andrei.popa@analog.com>

Author: andrei47w

docs/tests/general/core/add_dev_tests.rst

@@ -88,7 +88,7 @@ lists available local devices when initiated.
     - Scopy is installed on the system.
     - There is at least one IIO device connected to the system that has local 
       backend.
-    - OS: ANY.
+    - OS: Linux-x86_64.
 
 **Steps:**
     1. Open Scopy.

docs/tests/general/core/connection_tests.rst

@@ -62,7 +62,7 @@ Test 1: Verify the connection flow.
 **Steps:**
     1. Click on the device icon from device browser.
     2. Click on **Connect** button.
-        - **Expected result:** The **Disconnect** button appears, a status LED 
+        - **Expected result:** The **Disconnect** button appears, a status bar 
           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 

docs/tests/general/core/dev_tests.rst

@@ -467,7 +467,7 @@ properly.
     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 
+          device icons have a green status bar, 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.

docs/tests/general/core/emu_tests.rst

@@ -331,7 +331,7 @@ correctly (using pqm device).
     6. Click on **Verify** button.
         - **Expected result:** The compatible plugins page opens. The compatible 
           plugins are: PQMPlugin (checked), ADCPlugin, DACPlugin, DataLoggerPlugin, 
-          DebuggerPlugin.
+          DebuggerPlugin (checked).
         - **Actual result:**
 
 ..
@@ -378,7 +378,7 @@ correctly (using swiot_config device).
     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.
+          plugins are: SWIOTPlugin (checked), DataLoggerPlugin, DebuggerPlugin (checked).
         - **Actual result:**
 
 ..
@@ -426,7 +426,7 @@ correctly (using swiot_runtime device).
     6. Click on **Verify** button.
         - **Expected result:** The compatible plugins page opens. The compatible 
           plugins are: SWIOTPlugin (checked), ADCPlugin, DataLoggerPlugin, 
-          DebuggerPlugin, RegmapPlugin.
+          DebuggerPlugin (checked), RegmapPlugin.
         - **Actual result:**
 
 ..

docs/tests/general/core/hp_tests.rst

@@ -261,9 +261,11 @@ Test 6: Navigation using the buttons in the info page.
         - **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.
+        - **Actual result:**
     7. Click on the left arrow button.
         - **Expected result:** The "Welcome to Scopy" page is displayed and the 
           related button is highlighted.
+        - **Actual result:**
     8. Click on the left arrow button.
         - **Expected result:** The device's page is displayed and the device 
           icon is highlighted. 

docs/tests/general/core/license_about_page_tests.rst

@@ -144,8 +144,7 @@ Test 2: Check links from About Page
   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**
+    10. Click on the highlighted text **Documentation**
          - **Expected result:** A web browser window will open containing the
            documentation for Scopy.
          - **Actual result:**
@@ -154,8 +153,7 @@ Test 2: Check links from About Page
   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**
+    11. Click on the highlighted text **Support Forum**
          - **Expected result:** A web browser window will open containing a forum
            named `ADI EngineerZone`.
          - **Actual result:**

docs/tests/general/general_preferences_tests.rst

@@ -633,7 +633,7 @@ Test 12 - Auto-connect to previous session
    - Emulator tests
 
 **Preconditions:**  
-   - :ref:`Pluto.emu<pluto_emu_setup>`
+   - :ref:`Pluto.usb<pluto_emu_usb_setup>`
    - OS: ANY  
 
 **Steps:**  
@@ -876,7 +876,8 @@ Test 17 - Regularly scan for new devices
    - OS: ANY
 
 **Steps:**
-   1. Connect the Pluto to the machine via USB.  
+   1. Set preference to enabled.  
+   2. 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.
@@ -886,7 +887,7 @@ Test 17 - Regularly scan for new devices
   Actual test result goes here.
 ..
 
-   2. Repeat the steps with the preference disabled.
+   3. Repeat the steps with the preference disabled.
        - **Expected result:** Pluto should not appear automatically, 
          only when pressing the on-demand Scan button.
        - **Actual result:**
@@ -926,7 +927,7 @@ Test 18 - Session devices
    - OS: ANY  
 
 **Steps:**
-   1. After connecting to M2K, go to the preferences and press "Refresh."  
+   1. After connecting to Pluto, 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.  
@@ -972,8 +973,9 @@ Test 19 - Show plot FPS
    - OS: ANY  
 
 **Steps:**
-   1. Open Oscilloscope and run it.  
-   2. Open ADC - Time and run it.  
+   1. Set preference to enabled.  
+   2. Open Oscilloscope and run it.  
+   3. Open ADC - Time and run it.  
        - **Expected result:** Should show the FPS on the plot 
          (M2K may look different from other plugins).    
        - **Actual result:**
@@ -982,7 +984,7 @@ Test 19 - Show plot FPS
   Actual test result goes here.
 ..
 
-   3. Repeat the steps with the preference disabled.  
+   4. Repeat the steps with the preference disabled.  
        - **Expected result:** No FPS should be visible.    
        - **Actual result:**
 

docs/tests/general/instrument_detaching_tests.rst

@@ -29,7 +29,6 @@ Setup enviroment:
 **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
 ----------------------------------------------------------------------------------------------------

docs/tests/plugins/adc/adc_tests.rst

@@ -100,8 +100,7 @@ Test 1 - X-AXIS
   Actual test result goes here.
 ..
 
-   9. Change XMin to 200 and XMax to -100
-   10. Press Single
+   9. Change XMin to 300 and XMax to -100 (pressing Single will reset this setting)
         - **Expected result:** Plot labels should range from 300 to -100, with channel curves centered and between samples 200 and 0
         - **Actual result:**
 
@@ -683,8 +682,8 @@ plotting in the ADC plugin
   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
+   3. Set XMode to Frequency, XMin to 0.5 MHz, XMax to 2 MHz (pressing Single will reset this setting)
+       - **Expected result:** Plot labels should be from 0.5 MHz to 2 MHz
        - **Actual result:**
 
 ..