Release Manual Test Checklist

[andrewdavidmackenzie]

Test Blocks

HW Interaction

• Editing of pins connected to real HW
  • Input pin connected to switch
    • When set with pull-down it reports a low level
    • When set with pull-dup it reports a high level
    • While switch is pressed it reports a low in the UI and high when released
  • Output pin connected to LED
    • When loaded from config that has a value set in it, the LED changes to that value
    • When config set manually
      • if no value set in UI the LED does not change initial value
      • Setting to high with toggle sets the LED on
      • Setting to low with toggle sets the LED off
      • Clicking the clicker changes the value while pressed and back when released
• Same as above, but config is loaded from a file.

UI Interaction

• Pin can be set to be an Input
  • Pullup can be set to pull-up
  • Pullup can be set to None
  • Pullup can be set to pull-down
• Pin can be set to be an Output
  • Toggle changes the displayed value and stays there
  • Toggle changes back the displayed value and stays there
  • clicker changes value while pressed only
• Board layout toggle changes the layout and changes it back and window changes size and is not clipped
• Edit some pins and the config can be saved. If later reloaded from that file the config is loaded and applied including any output level set in the UI
• If no edit has been made, exiting by clicking on "X" in window manager exits immediately
• If an edit has been made, exiting by clicking on "X" in window manager causes exit dialog to show
  • If exit anyway is chosen the app exits
  • If cancel exit is chosen you return to the app
    • Trying to exit again will cause the dialog to show again
• If a config was loaded from file, exiting by clicking on "X" in window manager causes exit dialog to show
  • If after loading you make an edit, it behaves as above when edit was made without loading from file first
• If edit is made and you chose to load a config then the load config or cancel dialog is shown
  • If you cancel, you return to the app
  • If you chose to load anyway, the config is loaded and overwrites previous edits and app is in "no unsaved changes" state
    • Trying to exit should exit immediately

Networking (only applies to Piggui + Piglet scenarios)

• Piggui can disconnect from the current hardware that was connected at startup (fake or Pi hw)
  • The board layout is not shown
  • The option to connect to a remote piglet is shown
  • The option to reconnect to local hardware is shown
• Piggui can connect to piglet using Iroh with a nodeid via command line
• Piggui can connect to piglet using Iroh with a nodeid entered via dialog
• Piggui can connect to piglet using TCP with a ip:port via command line
• Piggui can connect to piglet using TCP with a ip:port entered via dialog

Scenarios

• Piggui only
  • 1 - Piggui on Macos/Linux/Windows with fake hw
  • 2 - Piggui on Pi with real GPIO hw
• Piggui and piglet
  • 3 - Piggui on Mac/Linux/Windows + Piglet on same machine
  • 4 - Piggui on Pi + Piglet on same machine
  • 5 - Piggui on Mac/Linux/Windows + Piglet on Pi

Manual Test Matrix

Execute the tests blocks in the specified scenario and click the checkbox when all pass.

• Scenario: 1 - Piggui on Macos/Linux/Windows with fake hw

• Test Blocks:

  • [x] UI Interaction

• Scenario: 2 - Piggui on Pi with real GPIO hw

• Test Blocks:

  • [x] HW Interaction
  • [x] UI Interaction

• Scenario: 3 - Piggui on Macos/Linux/Windows + Piglet on same machine

• Test Blocks:

  • [x] Networking

• Scenario: 4 - Piggui on Pi + Piglet on same machine

• Test Blocks:

  • [x] HW Interaction
  • [x] Networking

• Scenario: 5 - Piggui on Mac/Linux/Windows + Piglet on Pi

• Test Blocks:

  • [x] HW Interaction
  • [x] Networking

Already automated tests

• [X] piggui connects to piglet using Iroh by supplying nodeid at the command line
• [X] piggui connects to piglet using Tcp by supplying an IP and port number at the command line

[andrewdavidmackenzie]

All seems to work. Minor connection issue when connecting via tcp via dialog then switching to connect via iroh via dialog. Maybe tcp connection still open, or old tcp info in dialog was used?