kubuntu-council team mailing list archive

[Alexandre Ghiti <mp+427190@xxxxxxxxxxxxxxxxxx>]

Alexandre Ghiti has proposed merging ~alexghiti/ubuntu-manual-tests:int/alex/riscv_22.04.1 into ubuntu-manual-tests:main.

Requested reviews:
  Ubuntu Testcase Admins (ubuntu-testcase)

For more details, see:
https://code.launchpad.net/~alexghiti/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/427190
-- 
Your team Ubuntu Testcase Admins is requested to review the proposed merge of ~alexghiti/ubuntu-manual-tests:int/alex/riscv_22.04.1 into ubuntu-manual-tests:main.

diff --git a/testcases/image/1754_Install VisionFive b/testcases/image/1754_Install VisionFive
new file mode 100755
index 0000000..35dd5cc
--- /dev/null
+++ b/testcases/image/1754_Install VisionFive
@@ -0,0 +1,65 @@
+The scope of this test is to ensure that riscv64+visionfive image boots from SD card on StarFive VisionFive board
+
+<dl>
+    <dt>Flash downloaded image onto SD card</dt>
+        <dd>You can use Gnome Disks app to restore img.xz onto the SD card</dd>
+	<dd> Alternatively you can use xz -d to decompress, and then dd to copy the image to the SD card</dd>
+    <dt>Connect networking, serial console to the board</dt>
+        <dd>Ethernet cable for networking</dd>
+	<dd>FTDI adapter for serial console (pinout available here: https://rvspace.org/en/Product/VisionFive/Technical_Documents/VisionFive_Single_Board_Computer_Quick_Start_Guide)</dd>
+    <dt>Connect to the serial console</dt>
+        <dd>sudo screen /dev/ttyUSB1 115200</dd>
+    <dt>Power on the board</dt>
+        <dd>You should see U-BOOT menu</dd>
+	<dd>It should then boot default entry after a delay</dd>
+	<dd>After a while cloud-init will run</dd>
+	<dd>Then one will be able to login</dd>
+    <dt>Login and change password</dt>
+        <dd>Login using ubuntu for both username and password</dd>
+	<dd>Reenter ubuntu password again</dd>
+	<dd>Set new password</dd>
+	<dd>Confirm the new password</dd>
+    <dt>Perform WiFi testing</dt>
+	<dd>Make sure the WiFi device is enabled:</dd>
+		<dd>$ sudo apt get install network-manager</dd>
+		<dd>$ nmcli radio wifi</dd>
+		<dd>enabled</dd>
+	<dd>List AP:</dd>
+		<dd>$ nmcli dev wifi list</dd>
+    <dt>Perform generic testing</dt>
+        <dd>Check that apt update works</dd>
+	<dd>Run any command that is not installed, check that command-not-found recommends things to install</dd>
+	<dd>e.g. hello</dd>
+	<dd>Install a package and check that it works, e.g. hello</dd>
+    <dt>Perform snap testing</dt>
+        <dd>Install a snap and check that it works, e.g. hello</dd>
+    <dt>Perform HDMI testing</dt>
+	<dd>Plug an HDMI cable and make sure a prompt asking for login appears on the screen</dd>
+    <dt>Perform USB test</dt>
+	<dd>Plug a keyboard in and enter the login/password</dd>
+    <dt>Perform Bluetooth testing</dt>
+	<dd>Add the RISC-V PPA:</dd>
+	<dd>$ sudo add-apt-repository ppa:ubuntu-risc-v-team/develop</dd>
+	<dd>$ sudo apt update </dd>
+	<dd>Install the required packages:</dd>
+	<dd>$ sudo apt install linux-firmware-starfive brcm-patchram-plus-starfive</dd>
+	<dd>The installation may fail because the Bluetooth is flaky but the service installed by the brcm-patchram-plus-starfive package takes care of retrying</dd>
+	<dd>Check the brcm-patchram-plus-starfive.service status:</dd>
+	<dd>$ sudo systemctl status brcm-patchram-plus-starfive.service </dd>
+	<dd> Loaded: loaded (/lib/systemd/system/brcm-patchram-plus-starfive.service; enabled; vendor preset: enabled)
+     Active: active (running) since Wed 2022-06-22 13:42:33 UTC; 32min ago </dd>
+	<dd> ... </dd>
+	<dd>Additionally, you can check that the Bluetooth controller appears:</dd>
+	<dd>$ bluetoothctl </dd>
+	<dd> Agent registered </dd>
+	<dd> [CHG] Controller 70:4A:0E:95:C7:1B Pairable: yes </dd>
+	<dd>Note that the bluetooth requires GPIO toggling so if that works, we consider GPIO to work too.</dd>
+    <dt>Reboot</dt>
+	<dd>The board should reboot normally</dt>
+    <dt>Poweroff</dt>
+        <dd>Console messages should reach poweroff target</dd>
+	<dd>There should be final kernel dmsg powering off</dd>
+	<dd>Manually turn power-off from the board</dd>
+</dl>
+<strong>If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result.
+    If an action fails, or produces an unexpected result, please <a href="results#add_result">submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>. Please be sure to include the bug number when you <a href="results#add_result">submit</a> your result.</strong>
diff --git a/testcases/image/1755_Install Nezha b/testcases/image/1755_Install Nezha
new file mode 100755
index 0000000..5c15c84
--- /dev/null
+++ b/testcases/image/1755_Install Nezha
@@ -0,0 +1,41 @@
+The scope of this test is to ensure that riscv64+nezha image boots from SD card on Nezha board
+
+<dl>
+    <dt>Flash downloaded image onto SD card</dt>
+        <dd>You can use Gnome Disks app to restore img.xz onto the SD card</dd>
+	<dd> Alternatively you can use xz -d to decompress, and then dd to copy the image to the SD card</dd>
+    <dt>Connect networking, serial console to the board</dt>
+        <dd>Ethernet cable for networking</dd>
+	<dd>FTDI adapter for serial console (pinout available here: https://linuxgizmos.com/files/rvboards_nezha_detail.jpg)</dd>
+    <dt>Connect to the serial console</dt>
+        <dd>sudo screen /dev/ttyUSB1 115200</dd>
+    <dt>Power on the board</dt>
+        <dd>You should see U-BOOT menu</dd>
+	<dd>It should then boot default entry after a delay</dd>
+	<dd>After a while cloud-init will run</dd>
+	<dd>Then one will be able to login</dd>
+    <dt>Login and change password</dt>
+        <dd>Login using ubuntu for both username and password</dd>
+	<dd>Reenter ubuntu password again</dd>
+	<dd>Set new password</dd>
+	<dd>Confirm the new password</dd>
+    <dt>Perform generic testing</dt>
+        <dd>Check that apt update works</dd>
+	<dd>Run any command that is not installed, check that command-not-found recommends things to install</dd>
+	<dd>e.g. hello</dd>
+	<dd>Install a package and check that it works, e.g. hello</dd>
+    <dt>Perform snap testing</dt>
+        <dd>Install a snap and check that it works, e.g. hello</dd>
+    <dt>Perform HDMI testing</dt>
+	<dd>Plug an HDMI cable and make sure a prompt asking for login appears on the screen</dd>
+    <dt>Perform USB test</dt>
+	<dd>Plug a keyboard in and enter the login/password</dd>
+    <dt>Reboot</dt>
+	<dd>The board should reboot normally</dt>
+    <dt>Poweroff</dt>
+        <dd>Console messages should reach poweroff target</dd>
+	<dd>There should be final kernel dmsg powering off</dd>
+	<dd>Manually turn power-off from the board</dd>
+</dl>
+<strong>If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result.
+    If an action fails, or produces an unexpected result, please <a href="results#add_result">submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>. Please be sure to include the bug number when you <a href="results#add_result">submit</a> your result.</strong>