diff --git a/docs/unified-test-documentation/dasharo-compatibility/301-memory-hcl.md b/docs/unified-test-documentation/dasharo-compatibility/301-memory-hcl.md index 49029d6db5..870272eeeb 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/301-memory-hcl.md +++ b/docs/unified-test-documentation/dasharo-compatibility/301-memory-hcl.md @@ -1,6 +1,6 @@ # Dasharo compatibility: Memory HCL -## HCL001.001 Memory HCL - boot into OS (Ubuntu) +## HCL001.201 Memory HCL - boot into OS (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/303-custom-boot-menu-key.md b/docs/unified-test-documentation/dasharo-compatibility/303-custom-boot-menu-key.md index f648610446..4c3eaaf6c3 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/303-custom-boot-menu-key.md +++ b/docs/unified-test-documentation/dasharo-compatibility/303-custom-boot-menu-key.md @@ -1,6 +1,6 @@ # Dasharo compatibility: Custom Boot Keys -## CBK001.001 Custom Boot Menu Key +## CBK001.001 Custom boot menu key **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/306-usb-hid-and-msc-support.md b/docs/unified-test-documentation/dasharo-compatibility/306-usb-hid-and-msc-support.md index c18a5c8fc0..bdceb6c6ba 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/306-usb-hid-and-msc-support.md +++ b/docs/unified-test-documentation/dasharo-compatibility/306-usb-hid-and-msc-support.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## USB001.001 USB devices detection (firmware) +## USB001.001 USB devices detected in FW **Test description** @@ -42,15 +42,15 @@ correctly by the firmware and all basic keys work according to their labels. 1. Flash drive entry is listed in the boot menu. -## USB001.201 USB devices detection in OS (Ubuntu) +## USB001.201 USB devices detected by OS (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## USB001.301 USB devices detection in OS (Windows) +## USB001.301 USB devices detected by OS (Windows) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## USB002.201 USB keyboard detection (firmware) +## USB002.201 USB keyboard in OS (Ubuntu) **Test description** @@ -77,11 +77,7 @@ by the firmware and all basic keys work according to their labels. 1. All menus can be entered using the external USB keyboard. -## USB002.002 USB keyboard detection (Ubuntu) - -The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop - -## USB002.301 USB keyboard detection (Windows) +## USB002.301 USB keyboard in OS (Windows) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop @@ -89,6 +85,6 @@ The test is fully automated. Refer to https://github.com/Dasharo/open-source-fir The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## USB003.002 Upload 1GB file on USB storage (Windows) +## USB003.301 Upload 1GB file on USB storage (Windows) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-compatibility/307-freebsd-support.md b/docs/unified-test-documentation/dasharo-compatibility/307-freebsd-support.md index e90edaca3c..290f77271f 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/307-freebsd-support.md +++ b/docs/unified-test-documentation/dasharo-compatibility/307-freebsd-support.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BSD001.001 FreeBSD installation and boot +## BSD001.501 FreeBSD installation and boot (FreeBSD) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/308-debian-stable-and-ubuntu-lts-support.md b/docs/unified-test-documentation/dasharo-compatibility/308-debian-stable-and-ubuntu-lts-support.md index 45d5c62255..3cdbfb5f42 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/308-debian-stable-and-ubuntu-lts-support.md +++ b/docs/unified-test-documentation/dasharo-compatibility/308-debian-stable-and-ubuntu-lts-support.md @@ -117,7 +117,7 @@ from USB storage attached to the DUT. The `OPERATING_SYSTEM` login screen should be displayed. -## LBT003.001 Debian Stable installation on Hard Disk +## LBT003.208 Debian stable installation on Hard Disk (Debian) **Test description** @@ -144,7 +144,7 @@ on the hard disk on the DUT. The information about successful installation should be displayed. -## LBT003.002 Boot Debian from Hard Disk +## LBT003.208 Boot Debian from Hard Disk (Debian) **Test description** @@ -173,7 +173,7 @@ the hard disk on the DUT. The `OPERATING_SYSTEM` login screen should be displayed. -## LBT004.001 Ubuntu LTS installation on Hard Disk +## LBT004.201 Ubuntu LTS installation on Hard Disk (Ubuntu) **Test description** @@ -200,7 +200,7 @@ installed on the hard disk on the DUT. The information about successful installation should be displayed. -## LBT004.002 Boot Ubuntu From Hard Disk +## LBT005.201 Boot Ubuntu From Hard Disk (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/309-qubesos-support.md b/docs/unified-test-documentation/dasharo-compatibility/309-qubesos-support.md index a22c6eca11..053c9dc2f3 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/309-qubesos-support.md +++ b/docs/unified-test-documentation/dasharo-compatibility/309-qubesos-support.md @@ -7,7 +7,7 @@ 1. Proceed with the [Generic test setup: firmware](../generic-test-setup.md#firmware). -## QBS001.001 QubesOS installation +## QBS001.203 Qubes OS installation (Qubes OS) **Test description** @@ -32,7 +32,7 @@ This test aims to verify that QubesOS Stable distribution could be installed. The information about successful installation should be displayed. -## QBS001.002 Boot QubesOS +## QBS002.203 Boot Qubes OS (Qubes OS) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/310-fedora-support.md b/docs/unified-test-documentation/dasharo-compatibility/310-fedora-support.md index 8ed50d7e7f..aed3326438 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/310-fedora-support.md +++ b/docs/unified-test-documentation/dasharo-compatibility/310-fedora-support.md @@ -7,7 +7,7 @@ 1. Proceed with the [Generic test setup: firmware](../generic-test-setup.md#firmware). -## FED001.001 Fedora installation +## FED001.202 Fedora installation (Fedora) **Test description** @@ -32,7 +32,7 @@ This test aims to verify that Fedora Stable distribution could be installed. The information about successful installation should be displayed. -## FED001.002 Boot Fedora +## FED002.202 Boot Fedora (Fedora) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/312-nvme-support.md b/docs/unified-test-documentation/dasharo-compatibility/312-nvme-support.md index 17076e20f1..bfd5ee63ad 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/312-nvme-support.md +++ b/docs/unified-test-documentation/dasharo-compatibility/312-nvme-support.md @@ -1,6 +1,6 @@ # Dasharo Compatibility: NVMe support -## NVM001.001 NVMe support (firmware) +## NVM001.001 NVMe support in firmware **Test description** @@ -27,7 +27,7 @@ detect NVMe disk in the M.2 slot. 1. The NVMe disk should be listed on the bootable devices list. -## NVM001.201 NVMe support (Ubuntu) +## NVM001.201 NVMe support in OS (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-compatibility/315-network-boot.md b/docs/unified-test-documentation/dasharo-compatibility/315-network-boot.md index bbdfe94644..9acdb8de46 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/315-network-boot.md +++ b/docs/unified-test-documentation/dasharo-compatibility/315-network-boot.md @@ -8,7 +8,7 @@ [Generic test setup: firmware](../generic-test-setup.md#firmware). 1. The DUT should be connected to the Internet by using an Ethernet cable. -## PXE001.001 Dasharo Network Boot is bootable +## PXE001.001 Dasharo Network Boot is available **Test description** @@ -209,7 +209,7 @@ This test aims to verify that the `iPXE Shell` option in After configuring the network interfaces, connecting to the server and booting, `netboot.xyz` menu should appear. -## PXE007.001 iPXE network boot +## PXE007.001 Dasharo Network Boot over https not http **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/31A-windows-booting.md b/docs/unified-test-documentation/dasharo-compatibility/31A-windows-booting.md index a4c038c8c4..522e200cb1 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31A-windows-booting.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31A-windows-booting.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## WBT001.001 Windows 11 installation and boot +## WBT001.301 Windows 11 installation and boot (Windows) **Test description** @@ -39,7 +39,7 @@ and works properly. The Windows 11 login screen should be displayed. -## WBT002.001 Windows 10 installation and boot +## WBT002.301 Windows 10 installation and boot (Windows) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/31E-display-ports-and-lcd.md b/docs/unified-test-documentation/dasharo-compatibility/31E-display-ports-and-lcd.md index f3ded28553..1b7498f309 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31E-display-ports-and-lcd.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31E-display-ports-and-lcd.md @@ -39,11 +39,11 @@ during firmware execution phase. 1. Logo appears on the screen during firmware execution phase. -## DSP001.201 Internal LCD in OS (Ubuntu) +## DSP001.201 Internal display in OS (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## DSP001.301 Internal LCD in OS (Windows) +## DSP001.301 Internal display in OS (Windows) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-compatibility/31F-audio-subsystem.md b/docs/unified-test-documentation/dasharo-compatibility/31F-audio-subsystem.md index 1ab90e4d17..f445d62954 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31F-audio-subsystem.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31F-audio-subsystem.md @@ -58,7 +58,7 @@ Tigerlake HDMI The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## AUD002.201 Audio playback (Ubuntu) +## AUD002.201 Internal speaker audio playback (Ubuntu) **Test description** @@ -94,7 +94,7 @@ recordings. Sound should be played from the integrated speakers. -## AUD002.301 Audio playback (Windows) +## AUD002.301 Internal speaker audio playback (Windows) **Test description** @@ -124,7 +124,7 @@ recordings. Sound should be played from the integrated speakers. -## AUD003.201 Audio capture (Ubuntu) +## AUD003.201 Internal microphone audio capture (Ubuntu) **Test description** @@ -164,7 +164,7 @@ This test aims to verify that the audio subsystem is able to capture audio. The recorded audio clip is recorded correctly and played back. -## AUD003.301 Audio capture (Windows) +## AUD003.301 Internal microphone audio capture (Windows) **Test description** @@ -385,11 +385,11 @@ an external headset. 1. The result of the test after clicking the `Stop Test` bar should be more than 0% of the total volume. -## AUD007.201 HDMI Audio recognition (Ubuntu) +## AUD007.201 HDMI audio recognition (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## AUD007.301 HDMI Audio recognition (Windows) +## AUD007.301 HDMI audio recognition (Windows) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-compatibility/31G-ec-and-superio.md b/docs/unified-test-documentation/dasharo-compatibility/31G-ec-and-superio.md index 72bbea7c32..9be9c8c525 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31G-ec-and-superio.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31G-ec-and-superio.md @@ -1059,7 +1059,7 @@ system. 1. Pressing the button once should make laptop enter sleep mode. 1. The power LED should be blinking green, indicating the laptop is sleeping. -## ECR021.201 Keyboard (function key: RGB keyboard toggle) in OS (Ubuntu) +## ECR031.201 Keyboard (function key: RGB keyboard toggle) in OS (Ubuntu) **Test description** @@ -1088,7 +1088,7 @@ the operating system. 1. Pressing the button once should disable the keyboard backlight. 1. Pressing the button again should re-enable the keyboard backlight. -## ECR021.301 Keyboard (function key: RGB keyboard toggle) in OS (Windows) +## ECR031.301 Keyboard (function key: RGB keyboard toggle) in OS (Windows) **Test description** @@ -1117,7 +1117,7 @@ the operating system. 1. Pressing the button once should disable the keyboard backlight. 1. Pressing the button again should re-enable the keyboard backlight. -## ECR022.201 RGB keyboard next color FN key in OS (Ubuntu) +## ECR032.201 RGB keyboard next color FN key in OS (Ubuntu) **Test description** @@ -1147,7 +1147,7 @@ by the operating system. 1. Pressing the button once should switch the keyboard color. 1. All color modes according to product documentation should be accessible. -## ECR022.301 RGB keyboard next color FN key in OS (Windows) +## ECR032.301 RGB keyboard next color FN key in OS (Windows) **Test description** @@ -1177,7 +1177,7 @@ by the operating system. 1. Pressing the button once should switch the keyboard color. 1. All color modes according to product documentation should be accessible. -## ECR023.201 RGB keyboard brightness down FN key in OS (Ubuntu) +## ECR033.201 RGB keyboard brightness down FN key in OS (Ubuntu) **Test description** @@ -1205,7 +1205,7 @@ properly by the operating system. 1. Pressing the button once should lower the keyboard backlight -## ECR023.301 RGB keyboard brightness down FN key in OS (Windows) +## ECR033.301 RGB keyboard brightness down FN key in OS (Windows) **Test description** @@ -1233,7 +1233,7 @@ properly by the operating system. 1. Pressing the button once should lower the keyboard backlight. -## ECR024.201 RGB keyboard brightness up FN key in OS (Ubuntu) +## ECR034.201 RGB keyboard brightness up FN key in OS (Ubuntu) **Test description** @@ -1261,7 +1261,7 @@ properly by the operating system. 1. Pressing the button once should increase the keyboard backlight. -## ECR024.301 RGB keyboard brightness up FN key in OS (Windows) +## ECR034.301 RGB keyboard brightness up FN key in OS (Windows) **Test description** @@ -1318,7 +1318,7 @@ illuminates in firmware. 1. After cold-boot keyboard brightness and colors settings remain the same. -## ECR025.201 Permanent keyboard illumination after cold-boot (Ubuntu) +## ECR025.201 Permanent keyboard illumination after cold boot (Ubuntu) **Test description** @@ -1351,7 +1351,7 @@ illuminates in Ubuntu. 1. After cold-boot keyboard brightness and colors settings remain the same. -## ECR025.301 Permanent keyboard illumination after cold-boot (Windows) +## ECR025.301 Permanent keyboard illumination after cold boot (Windows) **Test description** @@ -1412,7 +1412,7 @@ illuminates in firmware. 1. After warm-boot keyboard brightness and colors settings remain the same. -## ECR026.201 Permanent keyboard illumination after warm-boot (Ubuntu) +## ECR026.201 Permanent keyboard illumination after warm boot (Ubuntu) **Test description** @@ -1444,7 +1444,7 @@ illuminates in Ubuntu. 1. After warm-boot keyboard brightness and colors settings remain the same. -## ECR026.301 Permanent keyboard illumination after warm-boot (Windows) +## ECR026.301 Permanent keyboard illumination after warm boot (Windows) **Test description** @@ -1719,15 +1719,7 @@ Windows. 1. The function keys `F1` - `F12` behave as if `Fn` key is pressed. -## ECR030.201 Charging until 98% battery level (Ubuntu) - -The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop - -## ECR031.201 Not charging between 95% and 98% levels (Ubuntu) - -The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop - -## ECR032.001 EC firmware sync in coreboot +## ECR032.001 EC firmware sync in coreboot blocked when AC not connected **Test description** @@ -1768,7 +1760,7 @@ This test verifies the automatic EC firmware update / sync feature in coreboot. 1. There should not be a pop-up indicating that the EC update failed for any reason. -## ECR033.001 EC firmware sync in coreboot blocked when AC not connected +## ECR033.001 EC power button watchdog **Test description** @@ -1807,7 +1799,7 @@ coreboot does not attempt to update the EC while an AC adapter is not connected. not proceed correctly, and asking them to reboot with an AC adapter connected. -## ECR034.001 EC power button watchdog +## ECR033.001 EC power button watchdog **Test description** @@ -1834,7 +1826,7 @@ can reset the EC. 1. The DUT should power off and on all within the 10 seconds of power button being pressed down -## ECR035.201 Soft Switch Microphone Key (Ubuntu) +## ECR030.201 Soft Switch Microphone Key (Ubuntu) **Test description** @@ -1865,7 +1857,7 @@ This test verifies that Fn+4 key combination for microphone soft switch works aforementioned bar which state is currently active as noise made will make the bar go back and forth if ON and completely still if OFF -## ECR034.301 Soft Switch Microphone Key (Windows) +## ECR030.301 Soft Switch Microphone Key (Windows) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/31H-usb-type-c.md b/docs/unified-test-documentation/dasharo-compatibility/31H-usb-type-c.md index e7f7c4d113..e69de29bb2 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31H-usb-type-c.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31H-usb-type-c.md @@ -1,1184 +0,0 @@ -# Dasharo Compatibility: USB-C/Thunderbolt support with charging and display - -## Test cases common documentation - -The test suite is mostly fully automated. Only manual test cases are documented. -Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop - -**Test setup** - -1. Proceed with the - [Generic test setup: firmware](../generic-test-setup.md#firmware). -1. Proceed with the - [Generic test setup: OS installation](../generic-test-setup.md#os-installation). -1. Proceed with the - [Generic test setup: OS preparation](../generic-test-setup.md#os-preparation). -1. Proceed with the - [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). - -## UTC001.001 USB Type-A charging capability - -**Test description** - -This test verifies that the USB-A ports are able to provide charging to a -connected smartphone. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Connect a phone to the USB Type-A port located on the left side of the laptop - using a USB cable. -1. Note the charging status on the phone screen. -1. Connect a phone to the USB Type-A port located on the right side of the laptop - using a USB cable. -1. Note the charging status on the phone screen. - -**Expected result** - -1. The smartphone should indicate that it's charging when connected to either - USB Type-A port. - -## UTC001.002 USB Type-A charging capability with ME disabled - -**Test description** - -This test verifies that the USB-A ports are able to provide charging to a -connected smartphone. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. - -**Test steps** - -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or - Disable (Soft) - if not, using the arrow keys and Enter, choose option - Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Connect a phone to the USB Type-A port located on the left side of the laptop - using a USB cable. -1. Note the charging status on the phone screen. -1. Connect a phone to the USB Type-A port located on the right side of the laptop - using a USB cable. -1. Note the charging status on the phone screen. - -**Expected result** - -1. The smartphone should indicate that it's charging when connected to either - USB Type-A port. - -## UTC002.001 Thunderbolt 4 USB Type-C power output - -**Test description** - -This test verifies that the Thunderbolt 4 port is able to provide charging to a -USB Type-C accessory. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Connect a phone to the Thunderbolt 4 USB Type-C port located on the left side - of the laptop using a USB cable. -1. Note the charging status on the phone screen. - -**Expected result** - -1. The smartphone should indicate that it's charging. - -## UTC002.002 Thunderbolt 4 USB Type-C power output with ME disabled - -**Test description** - -This test verifies that the Thunderbolt 4 port is able to provide charging to a -USB Type-C accessory. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. - -**Test steps** - -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Connect a phone to the Thunderbolt 4 USB Type-C port located on the left side - of the laptop using a USB cable. -1. Note the charging status on the phone screen. - -**Expected result** - -1. The smartphone should indicate that it's charging. - -## UTC007.001 USB Type-C docking station Triple display (Ubuntu) - -**Test description** - -This test aims to verify that the three display simultaneously connected to the -docking station is correctly recognized by the `OPERATING_SYSTEM`. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. Connect three displays using HDMI/DisplayPort cables, depending on the - specifications of the docking station. -1. The `USB-C docking station` connected to the USB-C port. - - > If the docking station is not directly connected to the DUT, but with a - > USB-C to USB-C cable, make sure it is full-featured cable (>=5Gbps) with - > 5A current capability. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Switch the display mode between `Mirror` and `Join Displays`. - -**Expected result** - -The image should be displayed on the three external displays in `Mirror` and -`Join Displays` modes. - -## UTC007.002 USB Type-C docking station Triple display (Windows) - -**Test description** - -This test aims to verify that the three display simultaneously connected to the -docking station is correctly recognized by the `OPERATING_SYSTEM`. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Windows - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. Connect three displays using HDMI/DisplayPort cables, depending on the - specifications of the docking station. -1. The `USB-C docking station` connected to the USB-C port. - - > If the docking station is not directly connected to the DUT, but with a - > USB-C to USB-C cable, make sure it is full-featured cable (>=5Gbps) with - > 5A current capability. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. If using more than one display, switch the display mode between `Duplicate` - and `Extend`. - -**Expected result** - -The image should be displayed on the three external displays in `Duplicate` and -`Extend` modes. - -## TMD007.001 USB Type-C docking station Triple display with ME disabled(Ubuntu) - -**Test description** - -This test aims to verify that the three display simultaneously connected to the -docking station is correctly recognized by the `OPERATING_SYSTEM`. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. Connect three displays using HDMI/DisplayPort cables, depending on the - specifications of the docking station. -1. The `USB-C docking station` connected to the USB-C port. - - > If the docking station is not directly connected to the DUT, but with a - > USB-C to USB-C cable, make sure it is full-featured cable (>=5Gbps) with - > 5A current capability. - -**Test steps** - -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Switch the display mode between `Mirror` and `Join Displays`. - -**Expected result** - -The image should be displayed on the three external displays in `Mirror` and -`Join Displays` modes. - -## UTC007.006 USB Type-C docking station Triple display with ME disabled(Windows) - -**Test description** - -This test aims to verify that the three display simultaneously connected to the -docking station is correctly recognized by the `OPERATING_SYSTEM`. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Windows - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. Connect three displays using HDMI/DisplayPort cables, depending on the - specifications of the docking station. -1. The `USB-C docking station` connected to the USB-C port. - - > If the docking station is not directly connected to the DUT, but with a - > USB-C to USB-C cable, make sure it is full-featured cable (>=5Gbps) with - > 5A current capability. - -**Test steps** - -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. If using more than one display, switch the display mode between `Duplicate` - and `Extend`. - -**Expected result** - -The image should be displayed on the three external displays in `Duplicate` and -`Extend` modes. - -## UTC011.001 USB Type-C docking station USB devices recognition (firmware) - -**Test description** - -This test aims to verify that the external USB devices connected to the docking -station are recognized correctly by the `FIRMWARE`. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. -1. The `USB storage` connected to the `USB-C docking station`. - -**Test steps** - -1. Power on the DUT. -1. Hold the `BIOS_MENU_KEY` to enter the BIOS Menu. -1. Check if the `USB storage` is available on the list. - -**Expected result** - -The `USB storage` is available which confirms successful recognition. - -## UTC011.004 USB Type-C docking station USB devices recognition ME disabled (firmware) - -**Test description** - -This test aims to verify that the external USB devices connected to the docking -station are recognized correctly by the `FIRMWARE`. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. -1. The `USB storage` connected to the `USB-C docking station`. - -**Test steps** - -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Hold the `BIOS_MENU_KEY` to enter the BIOS Menu. -1. Check if the `USB storage` is available on the list. - -**Expected result** - -The `USB storage` is available which confirms successful recognition. - -## UTC012.001 USB Type-C docking station USB keyboard (firmware) - -**Test description** - -This test aims to verify that the external USB keyboard connected to the docking -station is detected correctly by the `FIRMWARE` and all basic keys work -according to their labels. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. -1. The `external USB keyboard` connected to the docking station. - -**Test steps** - -1. Power on the DUT -1. Hold the `BIOS_MENU_KEY` to enter the Bios Menu. -1. Use the arrow keys, Esc key and the Enter key to navigate the menus. - -**Expected result** - -All menus can be entered using the external USB keyboard. - -## UTC013.001 USB Type-C docking station upload 1GB file on USB storage (Ubuntu) - -**Test description** - -This test aims to verify that the 1GB file can be transferred from the -`OPERATING_SYSTEM` to the `USB storage` connected to the docking station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. -1. The `USB storage` connected to the `USB-C docking station`. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Open a terminal window and run the following command to generate 1GB file: - - ```bash - openssl rand -out test_file.txt -base64 $(( 2**30 * 3/4 )) - ``` - -1. Read the path to the `USB storage` by running the following command: - - ```bash - lsblk - ``` - -1. Copy the generated file to the `USB storage` by running the following - command: - - ```bash - cp test_file.txt {path_to_usb_storage} - ``` - -1. Verify that the files are the same by running the following command: - - ```bash - sha256sum test_file.txt {path_to_usb_storage}/test_file.txt - ``` - -**Expected result** - -The output from the last command should contain 2 identical checksums: - -```bash -f46597c0c63a1eefb200d40edf654e52f10c3d5d21565886ad603fabaf8d39fb test_file.txt -f46597c0c63a1eefb200d40edf654e52f10c3d5d21565886ad603fabaf8d39fb {path_to_usb_storage}/test_file.txt -``` - -## UTC013.002 USB Type-C docking station upload 1GB file on USB storage(Windows) - -**Test description** - -This test aims to verify that the 1GB file can be transferred from the -`OPERATING_SYSTEM` to the `USB storage` connected to the docking station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Windows - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. -1. The `USB storage` connected to the `USB-C docking station`. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Open powershell as administrator and run the following command to generate - 1GB file: - - ```powershell - fsutil file createnew test_file.txt 1073741824 - ``` - -1. Read the drive letter assigned to the `USB storage` by running the following - command: - - ```powershell - (Get-Volume | where drivetype -eq removable).driveletter - ``` - -1. Copy the generated file to the `USB storage` by running the following - command: - - ```powershell - Copy-Item -Path C:\Windows\system32\test_file.txt {drive_letter}: - ``` - -1. Verify that the files are the same by running the following commands: - - ```powershell - Get-FileHash test_file.txt - Get-FileHash {drive_letter}:\test_file.txt - ``` - -**Expected result** - -The output from the last commands should have equal hash: - -```powershell -Algorithm Hash Path ---------- ---- ---- -SHA256 F46597C0C63A1EEFB200D40EDF654E52F10C3D5D21565886AD603FABAF8D39FB C\Windows\system3... -``` - -```powershell -Algorithm Hash Path ---------- ---- ---- -SHA256 F46597C0C63A1EEFB200D40EDF654E52F10C3D5D21565886AD603FABAF8D39FB E:\test_file.txt -``` - -## UTC013.003 USB Type-C docking station upload 1GB file on USB storage with ME disabled(Ubuntu) - -**Test description** - -This test aims to verify that the 1GB file can be transferred from the -`OPERATING_SYSTEM` to the `USB storage` connected to the docking station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. -1. The `USB storage` connected to the `USB-C docking station`. - -**Test steps** - -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Open a terminal window and run the following command to generate 1GB file: - - ```bash - openssl rand -out test_file.txt -base64 $(( 2**30 * 3/4 )) - ``` - -1. Read the path to the `USB storage` by running the following command: - - ```bash - lsblk - ``` - -1. Copy the generated file to the `USB storage` by running the following - command: - - ```bash - cp test_file.txt {path_to_usb_storage} - ``` - -1. Verify that the files are the same by running the following command: - - ```bash - sha256sum test_file.txt {path_to_usb_storage}/test_file.txt - ``` - -**Expected result** - -The output from the last command should contain 2 identical checksums: - -```bash -f46597c0c63a1eefb200d40edf654e52f10c3d5d21565886ad603fabaf8d39fb test_file.txt -f46597c0c63a1eefb200d40edf654e52f10c3d5d21565886ad603fabaf8d39fb {path_to_usb_storage}/test_file.txt -``` - -## UTC013.004 USB Type-C docking station upload 1GB file on USB storage with ME disabled(Windows) - -**Test description** - -This test aims to verify that the 1GB file can be transferred from the -`OPERATING_SYSTEM` to the `USB storage` connected to the docking station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Windows - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. -1. The `USB storage` connected to the `USB-C docking station`. - -**Test steps** - -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Open powershell as administrator and run the following command to generate - 1GB file: - - ```powershell - fsutil file createnew test_file.txt 1073741824 - ``` - -1. Read the drive letter assigned to the `USB storage` by running the following - command: - - ```powershell - (Get-Volume | where drivetype -eq removable).driveletter - ``` - -1. Copy the generated file to the `USB storage` by running the following - command: - - ```powershell - Copy-Item -Path C:\Windows\system32\test_file.txt {drive_letter}: - ``` - -1. Verify that the files are the same by running the following commands: - - ```powershell - Get-FileHash test_file.txt - Get-FileHash {drive_letter}:\test_file.txt - ``` - -**Expected result** - -The output from the last commands should have equal hash: - -```powershell -Algorithm Hash Path ---------- ---- ---- -SHA256 F46597C0C63A1EEFB200D40EDF654E52F10C3D5D21565886AD603FABAF8D39FB C\Windows\system3... -``` - -```powershell -Algorithm Hash Path ---------- ---- ---- -SHA256 F46597C0C63A1EEFB200D40EDF654E52F10C3D5D21565886AD603FABAF8D39FB E:\test_file.txt -``` - -## UTC016.001 USB Type-C docking station audio playback (Ubuntu) - -**Test description** - -This test aims to verify that the audio subsystem is able to playback audio -recordings by using the external headset speakers connected to the docking -station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Plug in a headset jack into the docking station. -1. When the `Select Audio Device` menu appears, select what type of external - device has been connected to the laptop (headset). -1. Open a terminal window and execute the following command: - - ```bash - pactl set-sink-mute alsa_output.pci-0000_00_1f.3.analog-stereo 0 - pactl set-sink-volume alsa_output.pci-0000_00_1f.3.analog-stereo 65535 - speaker-test - ``` - -**Expected result** - -Sound should be played from the external speakers. - -## UTC016.002 USB Type-C docking station audio playback (Windows) - -**Test description** - -This test aims to verify that the audio subsystem is able to playback audio -recordings by using the external headset speakers connected to the docking -station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Windows - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Plug in a headset jack into the docking station. -1. Find the `Speakers` icon in the bottom right part of the screen and click - it using the left mouse button to open volume menu. -1. After the `Which device did you plug in` menu appearing, select what type - of external device has been connected to the laptop (headset). -1. In the volume menu, click the rightmost part of it and note the result. - -**Expected result** - -Sound should be played from the external speakers. - -## UTC016.003 USB Type-C docking station audio playback with ME disabled(Ubuntu) - -**Test description** - -This test aims to verify that the audio subsystem is able to playback audio -recordings by using the external headset speakers connected to the docking -station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. - -**Test steps** - -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Plug in a headset jack into the docking station. -1. When the `Select Audio Device` menu appears, select what type of external - device has been connected to the laptop (headset). -1. Open a terminal window and execute the following command: - - ```bash - pactl set-sink-mute alsa_output.pci-0000_00_1f.3.analog-stereo 0 - pactl set-sink-volume alsa_output.pci-0000_00_1f.3.analog-stereo 65535 - speaker-test - ``` - -**Expected result** - -Sound should be played from the external speakers. - -## UTC016.004 USB Type-C docking station audio playback with ME disabled(Windows) - -**Test description** - -This test aims to verify that the audio subsystem is able to playback audio -recordings by using the external headset speakers connected to the docking -station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Windows - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. - -**Test steps** - -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Plug in a headset jack into the docking station. -1. Find the `Speakers` icon in the bottom right part of the screen and click - it using the left mouse button to open volume menu. -1. After the `Which device did you plug in` menu appearing, select what type - of external device has been connected to the laptop (headset). -1. In the volume menu, click the rightmost part of it and note the result. - -**Expected result** - -Sound should be played from the external speakers. - -## UTC017.001 USB Type-C docking station audio capture (Ubuntu) - -**Test description** - -This test aims to verify that the audio subsystem is able to capture audio -from external headset connected to the docking station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Plug in a headset jack into the docking station. -1. When the `Select Audio Device` menu appears, select what type of external - device has been connected to the laptop (headset). -1. Open a terminal window and execute the following command: - - ```bash - arecord -f S16_LE -d 10 -r 16000 /tmp/test-mic.wav - ``` - -1. Make some noise for the headset. For example, say something. -1. Execute the following command: - - ```bash - aplay /tmp/test-mic.wav - ``` - -**Expected result** - -The recorded audio clip is recorded correctly and played back. - -## UTC017.002 USB Type-C docking station audio capture (Windows) - -**Test description** - -This test aims to verify that the audio subsystem is able to capture audio -from external headset connected to the docking station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Windows - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Plug in a headset jack into the docking station. -1. After the `Which device did you plug in` menu appearing, select what type - of external device has been connected to the laptop (headset). -1. Find the `Speakers` icon in the bottom right part of the screen and click - it using the right mouse button then using the left mouse button - click `Sound Settings`. -1. Locate the `All sound devices` bar and click on it. -1. Select the `Microphone` position in the `Input devices` section. -1. Click on the `Start Test` bar in the `Input settings` section. -1. Create some noise for the DUT to capture and note the result. - For example, say something. -1. Click on the `Stop Test` bar. - -**Expected result** - -1. The `Input volume` bar located in the `Input settings` section should raise when - some noise is being created. -1. The result of the test after clicking the `Stop Test` bar should be more than - 0% of the total volume. - -## UTC017.003 USB Type-C docking station audio capture with ME disabled(Ubuntu) - -**Test description** - -This test aims to verify that the audio subsystem is able to capture audio -from external headset connected to the docking station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. - -**Test steps** - -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Plug in a headset jack into the docking station. -1. When the `Select Audio Device` menu appears, select what type of external - device has been connected to the laptop (headset). -1. Open a terminal window and execute the following command: - - ```bash - arecord -f S16_LE -d 10 -r 16000 /tmp/test-mic.wav - ``` - -1. Make some noise for the headset. For example, say something. -1. Execute the following command: - - ```bash - aplay /tmp/test-mic.wav - ``` - -**Expected result** - -The recorded audio clip is recorded correctly and played back. - -## UTC017.004 USB Type-C docking station audio capture with ME disabled(Windows) - -**Test description** - -This test aims to verify that the audio subsystem is able to capture audio -from external headset connected to the docking station. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Windows - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. The `USB-C docking station` connected to the USB-C port. - -**Test steps** - -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Plug in a headset jack into the docking station. -1. After the `Which device did you plug in` menu appearing, select what type - of external device has been connected to the laptop (headset). -1. Find the `Speakers` icon in the bottom right part of the screen and click - it using the right mouse button then using the left mouse button - click `Sound Settings`. -1. Locate the `All sound devices` bar and click on it. -1. Select the `Microphone` position in the `Input devices` section. -1. Click on the `Start Test` bar in the `Input settings` section. -1. Create some noise for the DUT to capture and note the result. - For example, say something. -1. Click on the `Stop Test` bar. - -**Expected result** - -1. The `Input volume` bar located in the `Input settings` section should raise when - some noise is being created. -1. The result of the test after clicking the `Stop Test` bar should be more than - 0% of the total volume. - -## UTC020.002 USB Type-C PD current limiting (Windows) - -**Test description** - -This test aims to verify that the power draw from a USB-C PD power supply does -not exceed the limits of the power supply's specifications. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Windows - -**Test steps** -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Download and install [ThrottleStop](https://www.techpowerup.com/download/techpowerup-throttlestop/) -1. Attach a 65W USB-C power supply, with the power meter between the power - supply and the laptop's Thunderbolt 4 port. -1. Open ThrottleStop. -1. Click the `Limits` button to open a window displaying current throttle status - and reasons. -1. Click the `TS Bench` button to open the benchmark window. -1. Start a benchmark with the default parameters (Normal, 16 threads, 120M, - Fixed MHz), while observing the power meter's display. -1. Repeat the step above 5 times, noting the maximum power draw shown on the - power meter each time. - -**Expected result** - -The power draw does not exceed more than 105% of the power supply's nominal -power. The power meter's display stays lit all the time, indicating that the -power supply's over-current protection was not triggered. When the power draw -approaches or exceeds 100% of the AC adapter's rating (65W), the field -`EDP Other` in the ThrottleStop Limit Reasons window is colored red. - -## UTC020.003 USB Type-C PD current limiting with ME disabled (Ubuntu) - -**Test description** - -This test aims to verify that the power draw from a USB-C PD power supply does -not exceed the limits of the power supply's specifications. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test steps** -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Attach a 65W USB-C power supply, with the power meter between the power - supply and the laptop's Thunderbolt 4 port. -1. Open a terminal window and run the following command, while observing the - power meter's display: - - ```bash - stress-ng -c 20 -t 5 - ``` - -1. Repeat the step above 5 times, noting the maximum power draw shown on the - power meter each time. - -**Expected result** - -The power draw does not exceed more than 105% of the power supply's nominal -power. The power meter's display stays lit all the time, indicating that the -power supply's over-current protection was not triggered. - -## UTC020.004 USB Type-C PD current limiting with ME disabled (Windows) - -**Test description** - -This test aims to verify that the power draw from a USB-C PD power supply does -not exceed the limits of the power supply's specifications. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Windows - -**Test steps** -1. Power on the DUT. -1. While the DUT is booting, hold the BIOS_SETUP_KEY to enter the UEFI Setup Menu. -1. Enter the Dasharo System Features menu using the arrow keys and Enter. -1. Enter the Intel Management Engine Options submenu. -1. Verify that the Intel ME mode option is in state Disable (HAP) or -Disable (Soft) - if not, using the arrow keys and Enter, choose option -Disable (HAP) or Disable (Soft). -1. Press F10 to save the changes. -1. If necessary - press Y to confirm saving the changes. -1. Go back to the main menu using the ESC key. -1. Select the Reset option to apply the settings and reboot. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Download and install [ThrottleStop](https://www.techpowerup.com/download/techpowerup-throttlestop/) -1. Attach a 65W USB-C power supply, with the power meter between the power - supply and the laptop's Thunderbolt 4 port. -1. Open ThrottleStop. -1. Click the `Limits` button to open a window displaying current throttle status - and reasons. -1. Click the `TS Bench` button to open the benchmark window. -1. Start a benchmark with the default parameters (Normal, 16 threads, 120M, - Fixed MHz), while observing the power meter's display. -1. Repeat the step above 5 times, noting the maximum power draw shown on the - power meter each time. - -**Expected result** - -The power draw does not exceed more than 105% of the power supply's nominal -power. The power meter's display stays lit all the time, indicating that the -power supply's over-current protection was not triggered. When the power draw -approaches or exceeds 100% of the AC adapter's rating (65W), the field -`EDP Other` in the ThrottleStop Limit Reasons window is colored red. diff --git a/docs/unified-test-documentation/dasharo-compatibility/31I-nvme-switching.md b/docs/unified-test-documentation/dasharo-compatibility/31I-nvme-switching.md index 3f760ce603..d5d9c6a5ed 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31I-nvme-switching.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31I-nvme-switching.md @@ -1,6 +1,6 @@ # Dasharo Compatibility: M.2 automatic SATA/NVMe switching support -## MSS001.001 M.2 automatic SATA/NVMe switching support (Ubuntu) +## MSS001.201 M.2 automatic SATA/NVMe switching support (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/31J-sleep-mode.md b/docs/unified-test-documentation/dasharo-compatibility/31J-sleep-mode.md index 209c24e84d..7cd2f793a5 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31J-sleep-mode.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31J-sleep-mode.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## SLM001.001 Sleep mode - battery monitoring (Ubuntu) +## SLM001.201 Sleep mode - battery monitoring (Ubuntu) **Test description** @@ -61,7 +61,7 @@ the OS. | 6h | 80% | | 24h (optional) | 57% | -## SLM000.002 Sleep mode - battery monitoring (Windows) +## SLM000.301 Sleep mode - battery monitoring (Windows) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/31M-emmc-support.md b/docs/unified-test-documentation/dasharo-compatibility/31M-emmc-support.md index c1e5fb19c3..b449e5d2dc 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31M-emmc-support.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31M-emmc-support.md @@ -1,6 +1,6 @@ # Dasharo Compatibility: eMMC support -## MMC001.001 eMMC support (Ubuntu) +## MMC001.201 eMMC support (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/31M-platform-suspend-and-resume.md b/docs/unified-test-documentation/dasharo-compatibility/31M-platform-suspend-and-resume.md index edb2947bbe..b77efdf1fc 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31M-platform-suspend-and-resume.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31M-platform-suspend-and-resume.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## SUSP001.201 Platform suspend and resume (Ubuntu, wakeup flag) +## SUSP001.201 Platform suspend and resume (Ubuntu) (wakeup flag) **Test description** @@ -116,7 +116,7 @@ is tested in this case. /usr/lib/pm-utils/sleep.d/000kernel-change resume suspend: success. ``` -## SUSP001.203 Platform suspend and resume (QubesOS, wakeup flag) +## SUSP001.203 Platform suspend and resume (Qubes OS) (wakeup flag) **Test description** @@ -176,7 +176,7 @@ this case. Feb 10 16:39:10 dom0 systemd-sleep[14729]: System resumed. ``` -## SUSP002.201 Platform suspend and resume (Ubuntu, press key) +## SUSP002.201 Platform suspend and resume (Ubuntu) (press key) **Test description** @@ -273,7 +273,7 @@ on the keyboard is tested in this case. /usr/lib/pm-utils/sleep.d/000kernel-change resume suspend: success. ``` -## SUSP002.203 Platform suspend and resume (QubesOS, press key) +## SUSP002.203 Platform suspend and resume (Qubes OS) (press key) **Test description** @@ -327,7 +327,7 @@ keyboard is tested in this case. Feb 10 16:39:10 dom0 systemd-sleep[14729]: System resumed. ``` -## SUSP003.201 Platform suspend and resume (Ubuntu, push power button) +## SUSP003.201 Platform suspend and resume (Ubuntu) (power button) **Test description** @@ -424,7 +424,7 @@ power button is tested in this case. /usr/lib/pm-utils/sleep.d/000kernel-change resume suspend: success. ``` -## SUSP003.203 Platform suspend and resume (QubesOS, push power button) +## SUSP003.203 Platform suspend and resume (Qubes OS) (power button) **Test description** @@ -478,7 +478,7 @@ tested in this case. Feb 10 16:39:10 dom0 systemd-sleep[14729]: System resumed. ``` -## SUSP004.201 Platform suspend and resume (Ubuntu, Wake-on-LAN) +## SUSP004.201 Platform suspend and resume (Ubuntu) (Wake-on-LAN) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/31R-pcie-ports.md b/docs/unified-test-documentation/dasharo-compatibility/31R-pcie-ports.md index f425e5fc75..d03adfb69a 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31R-pcie-ports.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31R-pcie-ports.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## PEX001.001 PCI Express card detection (Ubuntu) +## PEX001.201 PCI Express card detection (Ubuntu) **Test description** @@ -52,7 +52,7 @@ The output of the command should contain the plugged device name: The exact name and revision may be different depending on hardware configuration. -## PEX001.002 PCI Express card detection (Windows) +## PEX001.301 PCI Express card detection (Windows) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/31U-heads-bootloader-support.md b/docs/unified-test-documentation/dasharo-compatibility/31U-heads-bootloader-support.md index 30e676a833..e544a056f0 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31U-heads-bootloader-support.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31U-heads-bootloader-support.md @@ -7,7 +7,7 @@ 1. Proceed with the [Generic test setup: firmware](../generic-test-setup.md#firmware). -## HDS001.001 Heads installation +## HDS001.001 Install Heads **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/31V-petitboot-payload-support.md b/docs/unified-test-documentation/dasharo-compatibility/31V-petitboot-payload-support.md index ee77b3f4c6..2a279e5e21 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31V-petitboot-payload-support.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31V-petitboot-payload-support.md @@ -7,7 +7,7 @@ 1. Proceed with the [Generic test setup: firmware](../generic-test-setup.md#firmware). -## PBT001.001 Boot into Petitboot +## PBT002.001 Boot into Petitboot **Test description** @@ -32,7 +32,7 @@ menu. The `Petitbooot` menu screen should be displayed. -## PBT002.001 Read System Information from Petitboot +## PBT003.001 Read System Information from Petitboot **Test description** @@ -61,7 +61,7 @@ works correctly. After select `System Information` option, device information tree should be displayed. -## PBT003.001 Rescan Devices by Petitboot +## PBT004.001 Rescan Devices by Petitboot **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/31W-device-tree.md b/docs/unified-test-documentation/dasharo-compatibility/31W-device-tree.md index 52644d2c0a..dc65772047 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31W-device-tree.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31W-device-tree.md @@ -52,7 +52,7 @@ dedicated for coreboot. Example output: 00000000: 636f 7265 626f 6f74 00 coreboot ``` -## DVT002.001 Memory for coreboot is reserved (Ubuntu) +## DVT002.001 Memory for coreboot is reserved **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/320-fwupd-firmware-update.md b/docs/unified-test-documentation/dasharo-compatibility/320-fwupd-firmware-update.md index 2264af36a3..e69de29bb2 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/320-fwupd-firmware-update.md +++ b/docs/unified-test-documentation/dasharo-compatibility/320-fwupd-firmware-update.md @@ -1,82 +0,0 @@ -# Dasharo Compatibility: Firmware update using fwupd - -## Test cases common documentation - -**Test setup** - -1. Proceed with the - [Generic test setup: firmware](../generic-test-setup.md#firmware). -1. Proceed with the - [Generic test setup: OS installation](../generic-test-setup.md#os-installation). -1. Proceed with the - [Generic test setup: OS preparation](../generic-test-setup.md#os-preparation). -1. Proceed with the - [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -1. Install the `dmidecode` package: `sudo apt install dmidecode`. - -## FFW001.001 Firmware update by using fwupd - -**Test description** - -This test verify whether it is possible to update the firmware on the DUT by -using fwupd demon. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = Ubuntu - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. [Disable Secure Boot](../../unified-test-documentation/dasharo-security/206-secure-boot.md). - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Start firmware updating procedure by executing the following command in - the terminal: - - ```bash - sudo fwupdmgr update - ``` - -1. Reboot the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Open a terminal window and run the following command to verify results: - - ```bash - sudo dmidecode -t bios - ``` - -**Expected result** - -The output of `dmidecode` command should contain information about current -firmware. The current firmware version should be equal to the latest released -firmware version. - -Example output: - -```bash -BIOS Information - Vendor: 3mdeb - Version: Dasharo (coreboot+UEFI) v1.1.0 - Release Date: 03/24/2022 - ROM Size: 16 MB - Characteristics: - PCI is supported - PC Card (PCMCIA) is supported - BIOS is upgradeable - BIOS shadowing is allowed - Selectable boot is supported - ACPI is supported - USB legacy is supported - Targeted content distribution is supported - UEFI is supported - BIOS Revision: 1.1 - Firmware Revision: 0.0 -``` diff --git a/docs/unified-test-documentation/dasharo-compatibility/325-custom-boot-order.md b/docs/unified-test-documentation/dasharo-compatibility/325-custom-boot-order.md index fbbb6ef505..fe6f4b5930 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/325-custom-boot-order.md +++ b/docs/unified-test-documentation/dasharo-compatibility/325-custom-boot-order.md @@ -7,7 +7,7 @@ 1. Proceed with the [Generic test setup: firmware](../generic-test-setup.md#firmware). -## CBO001.001 Custom boot order (SeaBIOS) +## CBO001.102 Custom boot order (SeaBIOS) **Test description** @@ -54,7 +54,7 @@ Select boot device: 7. Payload [memtest] ``` -## CBO001.002 Custom boot order (edk2) +## CBO001.101 Custom Boot Order (EDK2 UEFI) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/326-dasharo-tools-suite.md b/docs/unified-test-documentation/dasharo-compatibility/326-dasharo-tools-suite.md index f3c095fadd..01e73c6385 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/326-dasharo-tools-suite.md +++ b/docs/unified-test-documentation/dasharo-compatibility/326-dasharo-tools-suite.md @@ -87,7 +87,7 @@ SUMMARY Thanks you for supporting Dasharo! ``` -## DTS003.001 DTS option power-off DUT works correctly +## DTS003.001 DTS option reboot DUT works correctly **Test description** @@ -116,7 +116,7 @@ turns off the DUT. The DUT should be turned off without any complications. -## DTS004.001 DTS option reboot DUT works correctly +## DTS004.001 DTS accessing shell works correctly **Test description** @@ -145,7 +145,7 @@ the DUT. The DUT should be rebooted without any complications. -## DTS005.001 DTS drop-to-shell option works correctly +## DTS005.001 Flash device from DTS shell by using flashrom works correctly **Test description** @@ -182,7 +182,7 @@ Entering shell, to leave type exit and press Enter or press LCtrl+D bash-5.1# ``` -## DTS006.001 Flash device from DTS shell by using flashrom works correctly +## DTS006.001 Flash device EC firmware by using DTS built-in script works correctly **Test description** @@ -249,7 +249,7 @@ Example output: Version: Dasharo (coreboot+UEFI) v1.1.0 ``` -## DTS007.001 Update device firmware from DTS Shell by using fwupd works correctly +## DTS007.001 Update device EC firmware by using DTS works correctly **Test description** @@ -302,7 +302,7 @@ Example output: Version: Dasharo (coreboot+UEFI) v1.1.0 ``` -## DTS008.001 Flash device EC firmware by using DTS built-in script works correctly +## DTS008.001 DTS option power-off DUT works correctly **Test description** @@ -336,7 +336,7 @@ firmware by using the built-in script in DTS. [documentation](https://docs.dasharo.com/dasharo-tools-suite/documentation/features/#ec-transition), should correspond to the latest version. -## DTS009.001 Update device EC firmware by using DTS works correctly +## DTS009.001 Update Dasharo firmware by using DTS via USB works correctly **Test description** @@ -371,7 +371,7 @@ firmware by using dasharo_ectool in DTS. [documentation](https://docs.dasharo.com/dasharo-tools-suite/documentation/features/#ec-update), should correspond to the binary version used. -## DTS010.001 Test firmware update in pre-release DTS over iPXE +## DTS010.001 Deploy Dasharo firmware by using DTS works correctly **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/326b-firmware-building-locally.md b/docs/unified-test-documentation/dasharo-compatibility/326b-firmware-building-locally.md index d9b48c6187..8221277dd5 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/326b-firmware-building-locally.md +++ b/docs/unified-test-documentation/dasharo-compatibility/326b-firmware-building-locally.md @@ -16,7 +16,7 @@ the relevant platform: * [NovaCustom laptops](../../unified/novacustom/building-manual.md) -## FLB001.001 Firmware locally build +## FLB001.201 Firmware locally build (Ubuntu) **Test description** @@ -48,7 +48,7 @@ platform. The `build` location should contain the binary file, which size is equal to the flash chip size. -## FLB002.001 Flash locally built firmware +## FLB002.201 Flash locally built firmware (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/341-pfSense-support.md b/docs/unified-test-documentation/dasharo-compatibility/341-pfSense-support.md index b047997238..a8b55ca4ed 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/341-pfSense-support.md +++ b/docs/unified-test-documentation/dasharo-compatibility/341-pfSense-support.md @@ -7,7 +7,7 @@ 1. Proceed with the [Generic test setup: firmware](../generic-test-setup.md#firmware). -## PFS001.001 pfSense stable (serial output) installation on Hard Disk +## PFS001.502 Install operating system on disk (pfSense) **Test description** @@ -33,7 +33,7 @@ on the hard disk on the DUT. The information about successful installation should be displayed. -## PFS001.002 Boot pfSense stable (serial output) from Hard Disk +## PFS002.502 Boot operating system from disk (pfSense) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md b/docs/unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md index e0dd69d51e..173155339f 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md +++ b/docs/unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md @@ -1,4 +1,4 @@ -# Dasharo Compatibility: OPNsense support +# Dasharo Compatibility: OPNSense support ## Test cases common documentation @@ -7,17 +7,17 @@ 1. Proceed with the [Generic test setup: firmware](../generic-test-setup.md#firmware). -## OPN001.001 OPNsense stable (serial output) installation on Hard Disk +## OPN001.503 Install operating system on disk (OPNSense) **Test description** -This test aims to verify that OPNsense stable (serial output) could be installed +This test aims to verify that OPNSense stable (serial output) could be installed on the hard disk on the DUT. **Test configuration data** 1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = OPNsense stable +1. `OPERATING_SYSTEM` = OPNSense stable **Test setup** @@ -33,17 +33,17 @@ on the hard disk on the DUT. The information about successful installation should be displayed. -## OPN001.002 Boot OPNsense stable (serial output) from Hard Disk +## OPN002.503 Boot operating system from disk (OPNSense) **Test description** -This test aims to verify that OPNsense stable serial could be booted from the +This test aims to verify that OPNSense stable serial could be booted from the hard disk on the DUT. **Test configuration data** 1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = OPNsense stable +1. `OPERATING_SYSTEM` = OPNSense stable **Test setup** @@ -62,17 +62,17 @@ hard disk on the DUT. The `OPERATING_SYSTEM` login screen should be displayed. -## OPN002.001 OPNsense stable (VGA output) installation on Hard Disk +## OPN002.001 OPNSense stable (VGA output) installation on Hard Disk **Test description** -This test aims to verify that OPNsense stable (VGA output) could be installed on +This test aims to verify that OPNSense stable (VGA output) could be installed on the hard disk on the DUT. **Test configuration data** 1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = OPNsense stable +1. `OPERATING_SYSTEM` = OPNSense stable **Test setup** @@ -88,17 +88,17 @@ the hard disk on the DUT. The information about successful installation should be displayed. -## OPN002.002 Boot OPNsense stable (VGA output) from Hard Disk +## OPN002.002 Boot OPNSense stable (VGA output) from Hard Disk **Test description** -This test aims to verify that OPNsense stable (VGA output) could be booted from +This test aims to verify that OPNSense stable (VGA output) could be booted from the hard disk on the DUT. **Test configuration data** 1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = OPNsense stable +1. `OPERATING_SYSTEM` = OPNSense stable **Test setup** diff --git a/docs/unified-test-documentation/dasharo-compatibility/346-SATA-hotplug-detection.md b/docs/unified-test-documentation/dasharo-compatibility/346-SATA-hotplug-detection.md index 09a4094770..800fe6b631 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/346-SATA-hotplug-detection.md +++ b/docs/unified-test-documentation/dasharo-compatibility/346-SATA-hotplug-detection.md @@ -57,7 +57,7 @@ detected after hot-plug. all hard disks connected to the device. 1. The refreshed list should contain additional item - mounted SATA disk. -## SHT001.002 SATA hot plug (Ubuntu) +## SHT001.201 SATA hot plug (Ubuntu) **Test description** @@ -106,7 +106,7 @@ Number Start End Size File system Name Flags (...) ``` -## SHT001.003 SATA hot plug (Windows) +## SHT001.301 SATA hot plug (Windows) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/357-bios-menu-function-keys.md b/docs/unified-test-documentation/dasharo-compatibility/357-bios-menu-function-keys.md index 273dea4b1d..915e9c34b4 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/357-bios-menu-function-keys.md +++ b/docs/unified-test-documentation/dasharo-compatibility/357-bios-menu-function-keys.md @@ -1,50 +1 @@ -# Dasharo Compatibility: BIOS menu function keys - -## Test cases common documentation - -**Test setup** - -1. Proceed with the - [Generic test setup: firmware](../generic-test-setup.md#firmware). - -## BMF001.001 Reset to Defaults option - -**Test description** - -This test aims to verify that the `F9` key feature properly reset to Defaults -all Dasharo System Features settings. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. - -**Test steps** - -1. Power on the DUT. -1. While booting, press the `SETUP_MENU_KEY` to enter Setup Menu. -1. Enter the `Dasharo System Features` menu option. -1. Enter the any of submenus eg. `Power Management Options`. -1. Verify that the `F9=Reset to Defaults` entry is displayed at the bottom of - the screen. -1. Press `F9` to reset options to defaults. -1. Press `Y` to confirm saving the changes. -1. Go back to the main menu using the `ESC` key. If necessary - press `Y` to - confirm saving the changes again. -1. Select the `Reset` option to apply the settings and reboot. -1. While booting, press the `SETUP_MENU_KEY` to enter Setup Menu. -1. Enter the `Dasharo System Features` menu option. -1. Check the state of each option in each submenu. -1. Note the results. - -**Expected result** - -1. The `F9=Reset to Defaults` entry is displayed in each submenu of Dasharo - System Features. -1. After using the `F9` key, all `Dasharo System Features` options should be set - to default. All options covered by this functionality can be found - [here](https://docs.dasharo.com/dasharo-menu-docs/dasharo-system-features/). +Replaced with RTD diff --git a/docs/unified-test-documentation/dasharo-compatibility/358-suspend-mechanism-switching-S0ix-S3.md b/docs/unified-test-documentation/dasharo-compatibility/358-suspend-mechanism-switching-S0ix-S3.md index 8d879fab09..59b9ace881 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/358-suspend-mechanism-switching-S0ix-S3.md +++ b/docs/unified-test-documentation/dasharo-compatibility/358-suspend-mechanism-switching-S0ix-S3.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## SMS001.001 Suspend to Idle (S0ix) check (Ubuntu) +## SMS001.201 Suspend to Idle (S0ix) check (Ubuntu) **Test description** @@ -62,7 +62,7 @@ Example output: [s2idle] shallow ``` -## SMS001.002 Suspend to RAM (S3) check (Ubuntu) +## SMS002.201 Suspend to RAM (S3) check (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/359-boot-blocking.md b/docs/unified-test-documentation/dasharo-compatibility/359-boot-blocking.md index eb6c04dacf..dedf5683e0 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/359-boot-blocking.md +++ b/docs/unified-test-documentation/dasharo-compatibility/359-boot-blocking.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BBB001.001 Boot blocking (charger disconnected) (Ubuntu) +## BBB001.201 Boot blocking (charger disconnected) (Ubuntu) **Test description** @@ -80,7 +80,7 @@ stress-ng: info: [25309] dispatching hogs: 16 cpu ![boot_block](../../images/battery_block_popup.jpg) -## BBB001.002 Boot blocking (charger connected) (Ubuntu) +## BBB002.201 Boot blocking (charger connected) (Ubuntu) **Test description** @@ -137,7 +137,7 @@ done 1. After reboot, the warning message should not appear and the DUT should boot normally. -## BBB002.001 Battery not connected warning (Firmware) +## BBB003.101 Battery not connected warning (EDK2 UEFI) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/362-dcu.md b/docs/unified-test-documentation/dasharo-compatibility/362-dcu.md index 7d2e36e8d4..45aaf95ff4 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/362-dcu.md +++ b/docs/unified-test-documentation/dasharo-compatibility/362-dcu.md @@ -1,6 +1,6 @@ # Dasharo Compatibility: Dasharo Configuration Utility -## DCU001.201 Change the UUID +## DCU001.201 Change the UUID (Ubuntu) **Test description** @@ -32,7 +32,7 @@ coreboot.rom` The UUID of the platform should be `96bcfa1a-42b4-6717-a44c-d8bbc18cbea4`, just as we had set it. -## DCU002.201 Change the serial number +## DCU002.201 Change the serial number (Ubuntu) **Test description** @@ -61,7 +61,7 @@ image can be changed using our utility. The serial number of the platform should be `D01234567`, just as we had set it. -## DCU003.201 Change the bootsplash logo +## DCU003.201 Change the bootsplash logo (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/S31-coreboot-fan-control.md b/docs/unified-test-documentation/dasharo-compatibility/S31-coreboot-fan-control.md index 63def1ba99..3d1f4f1377 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/S31-coreboot-fan-control.md +++ b/docs/unified-test-documentation/dasharo-compatibility/S31-coreboot-fan-control.md @@ -1,6 +1,6 @@ # Dasharo Compatibility: coreboot Fan Control -## CFN001.001 Check CPU entry temperature and CPU fan speed +## CFN001.201 CPU temperature and fan speed can be read (Ubuntu) **Test description** @@ -40,7 +40,7 @@ available. There are visible data for `fan1` and `temp7` which represents CPU fan speed and CPU temperature. -## CFN001.002 Check if increasing CPU temperature increases CPU fan speed +## CFN002.201 CPU fan speed increases if the temperature rises (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-compatibility/build-on-new-os.md b/docs/unified-test-documentation/dasharo-compatibility/build-on-new-os.md index 39689200cb..8370120b1f 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/build-on-new-os.md +++ b/docs/unified-test-documentation/dasharo-compatibility/build-on-new-os.md @@ -7,7 +7,7 @@ 1. Proceed with the [Generic test setup: firmware](../generic-test-setup.md#firmware). -## BNO001.001 Build on a newly installed OS (Ubuntu) +## BNO001.201 Build on a newly installed OS (Ubuntu) **Test description** @@ -31,7 +31,7 @@ in the case of testing on a Novacustom laptop. **Expected result** The build process should result in creating a rom file. -## BNO001.002 Boot (Ubuntu) +## BNO002.201 Boot (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-performance/400-coreboot-boot-measure.md b/docs/unified-test-documentation/dasharo-performance/400-coreboot-boot-measure.md index 392a95b6ab..9ead6f006d 100644 --- a/docs/unified-test-documentation/dasharo-performance/400-coreboot-boot-measure.md +++ b/docs/unified-test-documentation/dasharo-performance/400-coreboot-boot-measure.md @@ -16,7 +16,7 @@ [cloud](https://cloud.3mdeb.com/index.php/s/zTqkJQdNtJDo5Nd) to the DUT. 1. Disable Secure Boot. -## CBMEM001.201 coreboot booting time measure after coldboot (Ubuntu) +## CBMEM001.201 Serial boot time measure: coreboot booting time after coldboot (Ubuntu) **Test description** @@ -50,10 +50,10 @@ sudo ./cbmem -T The output of the command should contain the information about duration of all boot stages. -## CBMEM002.201 coreboot booting time measure after warmboot (Ubuntu) +## CBMEM002.201 Serial boot time measure: coreboot booting time after warmboot (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## CBMEM003.201 coreboot booting time measure after system reboot (Ubuntu) +## CBMEM003.201 Serial boot time measure: coreboot booting time after system reboot (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-performance/402-cpu-frequency.md b/docs/unified-test-documentation/dasharo-performance/402-cpu-frequency.md index 7188505854..905448694f 100644 --- a/docs/unified-test-documentation/dasharo-performance/402-cpu-frequency.md +++ b/docs/unified-test-documentation/dasharo-performance/402-cpu-frequency.md @@ -21,7 +21,7 @@ The test is fully automated. Refer to https://github.com/Dasharo/open-source-fir The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## CPF001.003 CPU not stuck on initial frequency (Heads+Debian) +## CPF001.209 CPU not stuck on initial frequency (Heads+Debian) **Test description** @@ -70,34 +70,34 @@ cpu MHz : 2800.000 cpu MHz : 2800.000 ``` -## CPF002.201 CPU runs on expected frequency (Ubuntu) +## CPF002.201 CPU not stuck on initial frequency (Battery) (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## CPF002.301 CPU runs on expected frequency (Windows) +## CPF002.301 CPU not stuck on initial frequency (Battery) (Windows) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## CPF003.201 CPU runs on expected frequency (Ubuntu, battery) +## CPF003.201 CPU not stuck on initial frequency (AC) (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## CPF003.301 CPU runs on expected frequency (Windows, battery) +## CPF003.301 CPU not stuck on initial frequency (AC) (Windows) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## CPF004.201 CPU with load runs on expected frequency (Ubuntu) +## CPF004.201 CPU not stuck on initial frequency (USB-PD) (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## CPF004.301 CPU with load runs on expected frequency (Windows) +## CPF004.301 CPU not stuck on initial frequency (USB-PD) (Windows) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## CPF005.201 CPU with load runs on expected frequency (Ubuntu, battery) +## CPF005.201 CPU runs on expected frequency (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## CPF005.301 CPU with load runs on expected frequency (Windows, battery) +## CPF005.301 CPU runs on expected frequency (Windows) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-performance/403-device-boot-measure.md b/docs/unified-test-documentation/dasharo-performance/403-device-boot-measure.md index a2014a1797..c470680fa9 100644 --- a/docs/unified-test-documentation/dasharo-performance/403-device-boot-measure.md +++ b/docs/unified-test-documentation/dasharo-performance/403-device-boot-measure.md @@ -1,131 +1 @@ -# Dasharo Performance: Device boot measure - -## Test cases common documentation - -**Test setup** - -1. Proceed with the - [Generic test setup: firmware](../generic-test-setup.md#firmware). -1. Proceed with the - [Generic test setup: OS installation](../generic-test-setup.md#os-installation). -1. Proceed with the - [Generic test setup: OS preparation](../generic-test-setup.md#os-preparation). -1. Proceed with the - [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). - -## DBM001.001 Device boot measure after coldboot (Ubuntu) - -**Test description** - -This test aims to verify whether the DUT boots after coldboot and how long this -process takes. This test case may be re-done several times to to average the -results and specify the platform stability. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = `Ubuntu` - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. - -**Test steps** - -1. Cut the power off while DUT is turned on. -1. Restore power and power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Open a terminal window and run the following command: - - ```bash - systemd-analyze - ``` - -1. Note the results. - -**Expected result** - -The output of the command should contain the information about duration of -all boot stages. - -## DBM002.001 Device boot measure after warmboot (Ubuntu) - -**Test description** - -This test aims to verify whether the DUT boots after warmboot and how long this -process takes. This test case may be re-done several times to to average the -results and specify the platform stability. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = `Ubuntu` - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Open a terminal window and run the following command: - - ```bash - systemd-analyze - ``` - -1. Note the results. - -**Expected result** - -The output of the command should contain the information about duration of -all boot stages. - -## DBM003.001 Device boot measure after reboot (Ubuntu) - -**Test description** - -This test aims to verify whether the DUT boots after system reboot and how long -this process takes. This test case may be re-done several times to to average -the results and specify the platform stability. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = `Ubuntu` - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. - -**Test steps** - -1. Power on the DUT. -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Open a terminal window and run the following command: - - ```bash - sudo reboot - ``` - -1. Boot into the system. -1. Log into the system by using the proper login and password. -1. Open a terminal window and run the following command: - - ```bash - systemd-analyze - ``` - -1. Note the results. - -**Expected result** - -The output of the command should contain the information about duration of -all boot stages. +Replaced with CBMEM tests diff --git a/docs/unified-test-documentation/dasharo-performance/405-fan-control-measure.md b/docs/unified-test-documentation/dasharo-performance/405-fan-control-measure.md index e77ed89b6e..d7da093016 100644 --- a/docs/unified-test-documentation/dasharo-performance/405-fan-control-measure.md +++ b/docs/unified-test-documentation/dasharo-performance/405-fan-control-measure.md @@ -19,7 +19,7 @@ apt-get install --assume-yes lm-sensors ``` -## FNM001.001 Fan does not stuck after coldboot (Ubuntu) +## FNM001.201 Fan does not stuck after coldboot (Ubuntu) **Test description** @@ -64,7 +64,7 @@ Example output: fan1: 1131 RPM (min = 329 RPM) ``` -## FNM002.001 Fan does not stuck after warmboot (Ubuntu) +## FNM002.201 Fan does not stuck after warmboot (Ubuntu) **Test description** @@ -108,7 +108,7 @@ Example output: fan1: 1131 RPM (min = 329 RPM) ``` -## FNM003.001 Fan does not stuck after reboot (Ubuntu) +## FNM003.201 Fan does not stuck after reboot (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-performance/406-custom-fan-curve.md b/docs/unified-test-documentation/dasharo-performance/406-custom-fan-curve.md index 30d9ceeedd..54e3bb4cac 100644 --- a/docs/unified-test-documentation/dasharo-performance/406-custom-fan-curve.md +++ b/docs/unified-test-documentation/dasharo-performance/406-custom-fan-curve.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## CFC001.001 Custom fan curve silent profile measure (Ubuntu) +## CFC001.201 Custom fan curve silent profile measure (Ubuntu) **Test description** @@ -63,7 +63,7 @@ The values of CPU temperature and fan speeds should match the [device specific instructions](#verifying-the-temperature-and-fan-speeds) on verifying the `Silent` fan curve. -## CFC002.001 Custom fan curve performance profile measure (Ubuntu) +## CFC002.201 Custom fan curve performance profile measure (Ubuntu) **Test description** @@ -114,7 +114,7 @@ The values of CPU temperature and fan speeds should match the [device specific instructions](#verifying-the-temperature-and-fan-speeds) on verifying the `Performance` fan curve. -## CFC003.001 Custom fan curve OFF profile measure (Ubuntu) +## CFC003.201 Custom fan curve OFF profile measure (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-performance/407-ubuntu-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/407-ubuntu-booting-performance-test.md index 2712bc1b1b..44f9d951e2 100644 --- a/docs/unified-test-documentation/dasharo-performance/407-ubuntu-booting-performance-test.md +++ b/docs/unified-test-documentation/dasharo-performance/407-ubuntu-booting-performance-test.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BUB001.001 Boot Ubuntu LTS from disk after cold-boot +## BUB001.201 Boot Ubuntu LTS from disk after cold-boot (Ubuntu) **Test description** @@ -43,7 +43,7 @@ DUT after cold-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BUB002.001 Boot Ubuntu LTS from disk after warm-boot +## BUB002.201 Boot Ubuntu LTS from disk after warm-boot (Ubuntu) **Test description** @@ -72,7 +72,7 @@ DUT after warm-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BUB003.001 Boot Ubuntu LTS from disk after reboot +## BUB003.201 Boot Ubuntu LTS from disk after reboot (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-performance/408-debian-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/408-debian-booting-performance-test.md index 5d5c40c66a..42a9bf6f66 100644 --- a/docs/unified-test-documentation/dasharo-performance/408-debian-booting-performance-test.md +++ b/docs/unified-test-documentation/dasharo-performance/408-debian-booting-performance-test.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BDE001.001 Boot Debian LTS from disk after cold-boot +## BDE001.208 Boot Debian LTS from disk after cold-boot (Debian) **Test description** @@ -43,7 +43,7 @@ on the DUT after cold-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BDE002.001 Boot Debian LTS from disk after warm-boot +## BDE002.208 Boot Debian LTS from disk after warm-boot (Debian) **Test description** @@ -72,7 +72,7 @@ on the DUT after warm-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BDE003.001 Boot Debian LTS from disk after reboot +## BDE003.208 Boot Debian LTS from disk after reboot (Debian) **Test description** diff --git a/docs/unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md index 73a715666a..91dc69b30a 100644 --- a/docs/unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md +++ b/docs/unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BFB001.001 Boot FreeBSD-RELEASE from disk after cold-boot +## BFB001.501 Boot FreeBSD-RELEASE from disk after cold-boot (FreeBSD) **Test description** @@ -43,7 +43,7 @@ on the DUT after cold-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BFB002.001 Boot FreeBSD-RELEASE from disk after warm-boot +## BFB002.501 Boot FreeBSD-RELEASE from disk after warm-boot (FreeBSD) **Test description** @@ -72,7 +72,7 @@ on the DUT after warm-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BFB003.001 Boot FreeBSD-RELEASE from disk after reboot +## BFB003.501 Boot FreeBSD-RELEASE from disk after reboot (FreeBSD) **Test description** diff --git a/docs/unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md index f8eee18254..3f8f03b0b7 100644 --- a/docs/unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md +++ b/docs/unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BPM001.001 Boot Proxmox Virtual Environment from disk after cold-boot +## BPM001.210 Boot Proxmox Virtual Environment from disk after cold-boot (Proxmox) **Test description** @@ -43,7 +43,7 @@ the DUT after cold-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BPM002.001 Boot Proxmox Virtual Environment from disk after warm-boot +## BPM002.210 Boot Proxmox Virtual Environment from disk after warm-boot (Proxmox) **Test description** @@ -72,7 +72,7 @@ the DUT after warm-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BPM003.001 Boot Proxmox Virtual Environment from disk after reboot +## BPM003.210 Boot Proxmox Virtual Environment from disk after reboot (Proxmox) **Test description** diff --git a/docs/unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md index 240d542013..c57942a584 100644 --- a/docs/unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md +++ b/docs/unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BUS001.001 Boot Ubuntu Server LTS from disk after cold-boot +## BUS001.201 Boot Ubuntu Server LTS from disk after cold-boot (Ubuntu) **Test description** @@ -43,7 +43,7 @@ on the DUT after cold-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BUS002.001 Boot Ubuntu Server LTS from disk after warm-boot +## BUS002.201 Boot Ubuntu Server LTS from disk after warm-boot (Ubuntu) **Test description** @@ -72,7 +72,7 @@ on the DUT after warm-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BUS003.001 Boot Ubuntu Server LTS from disk after reboot +## BUS003.201 Boot Ubuntu Server LTS from disk after reboot (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md index 9e80a2aac2..cc23f150c8 100644 --- a/docs/unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md +++ b/docs/unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md @@ -1,4 +1,4 @@ -# Dasharo Performance: OPNsense (serial output) booting performance test +# Dasharo Performance: OPNSense (serial output) booting performance test ## Test cases common documentation @@ -13,17 +13,17 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BOS001.001 Boot OPNsense (serial output) from disk after cold-boot +## BOS001.503 Boot OPNSense (serial output) from disk after cold-boot (OPNSense) **Test description** -This test aims to verify that OPNsense (serial output) could be booted from the +This test aims to verify that OPNSense (serial output) could be booted from the disk on the DUT after cold-boot. The test is performed in multiple iterations. **Test configuration data** 1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = OPNsense serial +1. `OPERATING_SYSTEM` = OPNSense serial **Test setup** @@ -43,17 +43,17 @@ disk on the DUT after cold-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BOS002.001 Boot OPNsense (serial output) from disk after warm-boot +## BOS002.503 Boot OPNSense (serial output) from disk after warm-boot (OPNSense) **Test description** -This test aims to verify that OPNsense (serial output) could be booted from the +This test aims to verify that OPNSense (serial output) could be booted from the disk on the DUT after warm-boot. The test is performed in multiple iterations. **Test configuration data** 1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = OPNsense serial +1. `OPERATING_SYSTEM` = OPNSense serial **Test setup** @@ -72,17 +72,17 @@ disk on the DUT after warm-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BOS003.001 Boot OPNsense (serial output) from disk after reboot +## BOS003.503 Boot OPNSense (serial output) from disk after reboot (OPNSense) **Test description** -This test aims to verify that OPNsense (serial output) could be booted from the +This test aims to verify that OPNSense (serial output) could be booted from the disk on the DUT after reboot. The test is performed in multiple iterations. **Test configuration data** 1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = OPNsense serial +1. `OPERATING_SYSTEM` = OPNSense serial **Test setup** diff --git a/docs/unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md index 98a13e954f..3570852273 100644 --- a/docs/unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md +++ b/docs/unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md @@ -1,4 +1,4 @@ -# Dasharo Performance: OPNsense (VGA output) booting performance test +# Dasharo Performance: OPNSense (VGA output) booting performance test ## Test cases common documentation @@ -13,17 +13,17 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BOV001.001 Boot OPNsense (VGA output) from disk after cold-boot +## BOV001.503 Boot OPNSense (VGA output) from disk after cold-boot (OPNSense) **Test description** -This test aims to verify that OPNsense (VGA output) could be booted from the +This test aims to verify that OPNSense (VGA output) could be booted from the disk on the DUT after cold-boot. The test is performed in multiple iterations. **Test configuration data** 1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = OPNsense VGA +1. `OPERATING_SYSTEM` = OPNSense VGA **Test setup** @@ -43,18 +43,18 @@ disk on the DUT after cold-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BOV002.001 Boot OPNsense (VGA output) stable from disk after warm-boot +## BOV002.503 Boot OPNSense (VGA output) from disk after warm-boot (OPNSense) **Test description** -This test aims to verify that OPNsense (VGA output) stable could be booted +This test aims to verify that OPNSense (VGA output) stable could be booted from the disk on the DUT after warm-boot. The test is performed in multiple iterations. **Test configuration data** 1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = OPNsense VGA +1. `OPERATING_SYSTEM` = OPNSense VGA **Test setup** @@ -73,18 +73,18 @@ iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BOV003.001 Boot OPNsense (VGA output) stable from disk after reboot +## BOV003.503 Boot OPNSense (VGA output) from disk after reboot (OPNSense) **Test description** -This test aims to verify that OPNsense (VGA output) stable could be booted +This test aims to verify that OPNSense (VGA output) stable could be booted from the disk on the DUT after reboot. The test is performed in multiple iterations. **Test configuration data** 1. `FIRMWARE` = Dasharo -1. `OPERATING_SYSTEM` = OPNsense VGA +1. `OPERATING_SYSTEM` = OPNSense VGA **Test setup** diff --git a/docs/unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md index 6f8751e29b..d9269be3de 100644 --- a/docs/unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md +++ b/docs/unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BPS001.001 Boot pfSense LTS CE (serial output) from disk after cold-boot +## BPS001.502 Boot pfSense LTS CE (serial output) from disk after cold-boot (pfSense) **Test description** @@ -44,7 +44,7 @@ iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BPS002.001 Boot pfSense LTS CE (serial output) from disk after warm-boot +## BPS002.502 Boot pfSense LTS CE (serial output) from disk after warm-boot (pfSense) **Test description** @@ -74,7 +74,7 @@ iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BPS003.001 Boot pfSense LTS CE (serial output) from disk after reboot +## BPS003.502 Boot pfSense LTS CE (serial output) from disk after reboot (pfSense) **Test description** diff --git a/docs/unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md index 7ddffa60df..9a4fb299e5 100644 --- a/docs/unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md +++ b/docs/unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BPV001.001 Boot pfSense LTS CE (VGA output) from disk after cold-boot +## BPV001.502 Boot pfSense LTS CE (VGA output) from disk after cold-boot (pfSense) **Test description** @@ -44,7 +44,7 @@ iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BPV002.001 Boot pfSense LTS CE (VGA output) from disk after warm-boot +## BPV002.502 Boot pfSense LTS CE (VGA output) from disk after warm-boot (pfSense) **Test description** @@ -74,7 +74,7 @@ iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BPV003.001 Boot pfSense LTS CE (VGA output) from disk after reboot +## BPV003.502 Boot pfSense LTS CE (VGA output) from disk after reboot (pfSense) **Test description** diff --git a/docs/unified-test-documentation/dasharo-performance/416-windows-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/416-windows-booting-performance-test.md index c0b197bb34..878888929e 100644 --- a/docs/unified-test-documentation/dasharo-performance/416-windows-booting-performance-test.md +++ b/docs/unified-test-documentation/dasharo-performance/416-windows-booting-performance-test.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## BWI001.001 Boot Windows from disk after cold-boot +## BWI001.301 Boot Windows from disk after cold-boot (Windows) **Test description** @@ -43,7 +43,7 @@ on the DUT after cold-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BWI002.001 Boot Windows from disk after warm-boot +## BWI002.301 Boot Windows from disk after warm-boot (Windows) **Test description** @@ -72,7 +72,7 @@ on the DUT after warm-boot. The test is performed in multiple iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BWI003.001 Boot Windows from disk after reboot +## BWI003.301 Boot Windows from disk after reboot (Windows) **Test description** diff --git a/docs/unified-test-documentation/dasharo-security/200-tpm-support.md b/docs/unified-test-documentation/dasharo-security/200-tpm-support.md index ba7d34a5be..f38d452a45 100644 --- a/docs/unified-test-documentation/dasharo-security/200-tpm-support.md +++ b/docs/unified-test-documentation/dasharo-security/200-tpm-support.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## TPM001.001 TPM Support (TPM events) +## TPM001.001 TPM Support (firmware) The test suite is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop @@ -25,38 +25,11 @@ The test suite is fully automated. Refer to https://github.com/Dasharo/open-sour The test suite is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## TPM001.004 TPM Support (BIOS) - -**Test description** - -This test aims to verify that the TPM is initialized correctly. - -**Test configuration data** - -1. `FIRMWARE` = Dasharo - -**Test setup** - -1. Proceed with the - [Test cases common documentation](#test-cases-common-documentation) section. -1. Disable Secure Boot. - -**Test steps** - -1. Power on the DUT. -1. Boot into the BIOS. -1. Enter Device Manager. -1. Enter TCG2 Configuration - -**Expected result** - -`Current TPM Device` should contain `TPM 2.0` or `TPM 1.2`. - -## TPM002.201 Verify TPM version (Ubuntu) +## TPM002.201 Verify TPM Version (Ubuntu) The test suite is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## TPM002.301 Verify TPM version (Windows) +## TPM002.301 Verify TPM Version (Windows) The test suite is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-security/200-tpm2-commands.md b/docs/unified-test-documentation/dasharo-security/200-tpm2-commands.md index 3a68cdeedc..29d6d58301 100644 --- a/docs/unified-test-documentation/dasharo-security/200-tpm2-commands.md +++ b/docs/unified-test-documentation/dasharo-security/200-tpm2-commands.md @@ -28,7 +28,7 @@ If not, run `tpm2_pcrallocate` and reboot the system. -## TPMCMD001.001 Check if both SHA1 and SHA256 PCRs are enabled (Ubuntu) +## TPMCMD001.201 Check if both SHA1 and SHA256 PCRs are enabled (Ubuntu) **Test description** @@ -68,7 +68,7 @@ selected-pcrs: - sha512: [ 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23 ] ``` -## TPMCMD002.001 PCRREAD Function Verification (Ubuntu) +## TPMCMD002.201 PCRREAD Function Verification (Ubuntu) **Test description** @@ -129,7 +129,7 @@ The output should contain values of various PCR registers, example: (...) ``` -## TPMCMD003.001 PCREXTEND And PCRRESET Functions (Ubuntu) +## TPMCMD003.201 PCREXTEND And PCRRESET Functions (Ubuntu) **Test description** @@ -197,7 +197,7 @@ accordingly. -## TPMCMD003.002 PCREXTEND And PCRRESET Functions - locality protections (Ubuntu) +## TPMCMD004.201 PCREXTEND And PCRRESET Functions - locality protections (Ubuntu) @@ -247,7 +247,7 @@ Warning should appear after the first step and second step, the eighteenth bank should contain `0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF` after the third step. -## TPMCMD004.001 PCREVENT Function (Ubuntu) +## TPMCMD005.201 PCREVENT Function (Ubuntu) **Test description** @@ -311,7 +311,7 @@ This test aims to verify that the PCREVENT function is working properly. Hashes calculated manually should match those calculated by `tpm2_event`. -## TPMCMD005.001 CREATEPRIMARY Function Verification (Ubuntu) +## TPMCMD006.201 CREATEPRIMARY Function Verification (Ubuntu) **Test description** @@ -375,7 +375,7 @@ rsa: a463fa1da7b5515481ad7171cad9402d1a4a0864cb918035733dc9095daa9798279cbf82fac 289c9af6d3d319f049b60e3ae1f7e6b66d5c4371cc409b1a49f837dbad80f6184b7ab37c7c8118d12de502bbb3c4a38fdfad5a12a03d496079d3b97d25d0bb05bc0b00a6b4c34df02d02ba31861e68aa188e0394df57bb84a0a1fb46b41d53ec008f40e272d50b16ec5f7cbd8f8a92a72bcff7a2f17d6e122c6539b62f51c8b4881f412c4de814362725895 ``` -## TPMCMD006.001 NVDEFINE and NVUNDEFINE Functions Verification (Ubuntu) +## TPMCMD007.201 NVDEFINE and NVUNDEFINE Functions Verification (Ubuntu) **Test description** @@ -436,7 +436,7 @@ The data should be successfully written and read using TPM Non-Volatile index but it also should not be read successfully after the TPM Non-Volatile index has been undefined. -## TPMCMD007.001 CREATE Function (Ubuntu) +## TPMCMD008.201 CREATE Function (Ubuntu) **Test description** @@ -475,7 +475,7 @@ and public portions to the paths specified via `-u` and `-r` respectively. The public and secret portions should be sealed without any issues. -## TPMCMD007.002 CREATELOADED Function (Ubuntu) +## TPMCMD009.201 CREATELOADED Function (Ubuntu) **Test description** @@ -514,7 +514,7 @@ path specified via `-c`. The key should be stored in TPM without any issues. -## TPMCMD008.001 Signing the file (Ubuntu) +## TPMCMD010.201 Signing the file (Ubuntu) **Test description** @@ -570,7 +570,7 @@ Check whether the TPM supports file signing. The file should be signed successfully. -## TPMCMD009.001 Encryption and Decryption of the file (Ubuntu) +## TPMCMD011.201 Encryption and Decryption of the file (Ubuntu) **Test description** @@ -625,7 +625,7 @@ Check whether the TPM supports the encryption and decryption of the file. The file should be encrypted and then decrypted successfully. Content of `secret.data` and `secret.dec` should be the same. -## TPMCMD010.001 Hashing the file (Ubuntu) +## TPMCMD012.201 Hashing the file (Ubuntu) **Test description** @@ -659,7 +659,7 @@ Check whether the TPM supports file hashing. The hashes should be created successfully. -## TPMCMD011.001 Performing HMAC operation on the file (Ubuntu) +## TPMCMD013.201 Performing HMAC operation on the file (Ubuntu) **Test description** @@ -712,7 +712,7 @@ Check whether the TPM supports HMAC operation. Verify that HMAC operation ended successfully. -## TPMCMD012.001 Sealing and Unsealing the file without Policy (Ubuntu) +## TPMCMD014.201 Sealing and Unsealing the file without Policy (Ubuntu) **Test description** @@ -758,7 +758,7 @@ This test verifies TPM sealing functionality. The output in step 6 should be the equal to the content of `seal.dat`. -## TPMCMD013.001 Sealing and Unsealing with Policy - Password Only (Ubuntu) +## TPMCMD015.201 Sealing and Unsealing with Policy - Password Only (Ubuntu) **Test description** @@ -807,7 +807,7 @@ Check whether the TPM supports sealing and unsealing using password policy. The output in step 6 should be the equal to the content of `seal.dat`. -## TPMCMD013.002 Sealing and Unsealing with Policy - PCR Only (Ubuntu) +## TPMCMD016.201 Sealing and Unsealing with Policy - PCR Only (Ubuntu) **Test description** @@ -856,7 +856,7 @@ Check whether the TPM supports sealing and unsealing using PCR policy. The output in step 6 should be the equal to the content of `seal.dat`. -## TPMCMD013.003 Sealing and unsealing with Policy - Password and PCR (Ubuntu) +## TPMCMD017.201 Sealing and unsealing with Policy - Password and PCR (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-security/201-verified-boot.md b/docs/unified-test-documentation/dasharo-security/201-verified-boot.md index cefe982b0f..4352a65c49 100644 --- a/docs/unified-test-documentation/dasharo-security/201-verified-boot.md +++ b/docs/unified-test-documentation/dasharo-security/201-verified-boot.md @@ -13,34 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## VBO006.001 Verified boot support (firmware) - -**Test description** - -Verified Boot is a method of verifying that the firmware components come from a -trusted source. This test aims to confirm that verified boot is enabled and -functional. - -**Test setup** - -1. Proceed with the - [Generic test setup: firmware](../generic-test-setup.md#firmware). -1. Disable Secure Boot. - -**Test steps** - -1. Power on the DUT. -1. Read coreboot loading logs. - -**Expected result** - -The logs should indicate that vboot is enabled and verstage has been entered: - -```text -VBOOT: Loading verstage. -``` - -## VBO006.002 Verified boot support (Ubuntu) +## VBO006.201 Verified boot support (Ubuntu) **Test description** @@ -86,33 +59,7 @@ PCR-0 2547cc736e951fa4919853c43ae890861a3b3264000000000000000000000000 SHA256 [V PCR-1 e3324765a25f8a59c7c20cc35c1c33a8ab384159d2b40a269246b0b4491cdf89 SHA256 [VBOOT: GBB HWID] ``` -## VBO007.001 Verified boot: Booting from Slot A (firmware) - -**Test description** - -If the signatures for firmware stored in vboot Slot A are correct, vboot should -proceed to boot from Slot A. - -**Test setup** - -1. Proceed with the - [Generic test setup: firmware](../generic-test-setup.md#firmware). -1. Disable Secure Boot. - -**Test steps** - -1. Power on the DUT. -1. Read coreboot loading logs. - -**Expected result** - -The logs should indicate that vboot has chosen to boot from slot A: - -```text -Slot A is selected -``` - -## VBO007.002 Verified boot: Booting from Slot A (Ubuntu) +## VBO007.201 Booting from Slot A (Ubuntu) **Test description** @@ -152,7 +99,7 @@ slot A: Slot A is selected ``` -## VBO008.001 Verified boot: Booting from Recovery (Ubuntu) +## VBO008.201 Booting from Recovery (Ubuntu) **Test description** @@ -290,7 +237,7 @@ command: After pressing `ENTER` the DUT should immediately move to the next stages of booting. -## VBO011.001 Booting after flashing with valid binary (Ubuntu) +## VBO011.001 Recovery popup is not displayed when correctly signed firmware is flashed in RW_A **Test description** diff --git a/docs/unified-test-documentation/dasharo-security/206-secure-boot.md b/docs/unified-test-documentation/dasharo-security/206-secure-boot.md index e9d315fc1d..162a9adeb4 100644 --- a/docs/unified-test-documentation/dasharo-security/206-secure-boot.md +++ b/docs/unified-test-documentation/dasharo-security/206-secure-boot.md @@ -31,7 +31,7 @@ flashing the platform with the Dasharo firmware is correct. The `Secure Boot State` field should inform that the current state of Secure Boot is `Disabled`. -## SBO002.001 UEFI Secure Boot (Ubuntu) +## SBO002.201 UEFI Secure Boot (Ubuntu) **Test description** @@ -94,7 +94,7 @@ The output of the command should contain the line: secureboot: Secure boot enabled ``` -## SBO002.002 UEFI Secure Boot (Windows) +## SBO002.301 UEFI Secure Boot (Windows) **Test description** @@ -149,7 +149,7 @@ enabled: True ``` -## SBO003.001 Attempt to boot file with the correct key from Shell (firmware) +## SBO003.101 Attempt to boot file with the correct key from Shell (EDK2 UEFI) **Test description** @@ -217,7 +217,7 @@ the output) and the output of the command shows file content. Example output: Hello, world! ``` -## SBO004.001 Attempt to boot file without the key from Shell (firmware) +## SBO004.101 Attempt to boot file without the key from Shell (EDK2 UEFI) **Test description** @@ -273,7 +273,7 @@ denied is displayed. Example output: Command Error Status: Access Denied ``` -## SBO005.001 Attempt to boot file with the wrong-signed key from Shell (firmware) +## SBO005.101 Attempt to boot file with the wrong-signed key from Shell (EDK2 UEFI) **Test description** @@ -330,7 +330,7 @@ denied is displayed. Example output: Command Error Status: Access Denied ``` -## SBO006.001 Reset Secure Boot Keys option availability (firmware) +## SBO006.101 Reset Secure Boot Keys option availability (EDK2 UEFI) **Test description** @@ -361,7 +361,7 @@ after flashing the platform with the Dasharo firmware. The `Reset Secure Boot Keys` option should be listed after entering the key management submenu. -## SBO007.001 Attempt to boot the file after restoring keys to default (firmware) +## SBO007.101 Attempt to boot the file after restoring keys to default (EDK2 UEFI) **Test description** @@ -477,7 +477,7 @@ Command Error Status: Access Denied After selecting the `Reset Secure Boot Keys` option, the Secure boot state should be automatically enabled. -## SBO008.001 Attempt to enroll the key in the incorrect format (firmware) +## SBO008.101 Attempt to enroll the key in the incorrect format (EDK2 UEFI) **Test description** @@ -1069,7 +1069,7 @@ image. File does not boot correctly: `Command Error Status: Access Denied`. -## SBO012.001 Boot OS Signed And Enrolled From Inside System (Ubuntu) +## SBO012.201 Boot OS Signed And Enrolled From Inside System (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-security/207-boot-guard-support.md b/docs/unified-test-documentation/dasharo-security/207-boot-guard-support.md index ad67c3ffe3..bc368919ab 100644 --- a/docs/unified-test-documentation/dasharo-security/207-boot-guard-support.md +++ b/docs/unified-test-documentation/dasharo-security/207-boot-guard-support.md @@ -1,6 +1,6 @@ # Dasharo Security: Boot Guard support -## BGS001.001 Boot Guard support (Ubuntu) +## BGS001.201 Boot Guard support (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-security/20F-me-neuter.md b/docs/unified-test-documentation/dasharo-security/20F-me-neuter.md index 21ef4a2feb..3e1992ddf0 100644 --- a/docs/unified-test-documentation/dasharo-security/20F-me-neuter.md +++ b/docs/unified-test-documentation/dasharo-security/20F-me-neuter.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## MNE001.001 Intel ME mode option is available and has the correct default state +## MNE001.001 ME disable option is available and has the correct default state **Test description** @@ -42,11 +42,11 @@ platform with the Dasharo firmware is correct. The `Intel ME mode` field should inform that the current state is `Enabled`. -## MNE002.201 Intel ME mode option Enabled works correctly (Ubuntu) +## MNE002.201 ME disable option off works correctly (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## MNE004.201 Intel ME mode option Disable (HAP) works correctly (Ubuntu) +## MNE004.201 ME disable HAP bit option works correctly (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-security/20L-early-boot-dma-protection.md b/docs/unified-test-documentation/dasharo-security/20L-early-boot-dma-protection.md index bd3f63fb92..0b2a15813a 100644 --- a/docs/unified-test-documentation/dasharo-security/20L-early-boot-dma-protection.md +++ b/docs/unified-test-documentation/dasharo-security/20L-early-boot-dma-protection.md @@ -16,7 +16,7 @@ [cloud](https://cloud.3mdeb.com/index.php/s/zTqkJQdNtJDo5Nd) to the DUT. 1. Disable Secure Boot. -## EDP001.001 Enable early Boot DMA Protection support +## EDP001.001 Enable early boot DMA protection support **Test description** @@ -112,7 +112,7 @@ Indicate that VT-D engine 1 had PMR enabled earlier, which is expected. If all above conditions are met, test pass. -## EDP002.001 Disable early Boot DMA Protection support +## EDP002.001 Disable early boot DMA protection support **Test description** diff --git a/docs/unified-test-documentation/dasharo-security/20O-SMM-bios-write-protection.md b/docs/unified-test-documentation/dasharo-security/20O-SMM-bios-write-protection.md index 34dc35382e..6a536e2f90 100644 --- a/docs/unified-test-documentation/dasharo-security/20O-SMM-bios-write-protection.md +++ b/docs/unified-test-documentation/dasharo-security/20O-SMM-bios-write-protection.md @@ -14,7 +14,7 @@ [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). 1. Disable Secure Boot. -## SMM001.001 SMM BIOS write protection enabling (Ubuntu) +## SMM001.201 SMM BIOS write protection enabling (Ubuntu) **Test description** @@ -70,7 +70,7 @@ Example output: Enabling flash write... Warning: BIOS region SMM protection is enabled! ``` -## SMM002.001 SMM BIOS write protection disabling (Ubuntu) +## SMM002.201 SMM BIOS write protection disabling (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/dasharo-security/20P-boot-menu.md b/docs/unified-test-documentation/dasharo-security/20P-boot-menu.md index 3da76f47b7..0a552f6087 100644 --- a/docs/unified-test-documentation/dasharo-security/20P-boot-menu.md +++ b/docs/unified-test-documentation/dasharo-security/20P-boot-menu.md @@ -7,7 +7,7 @@ 1. Proceed with the [Generic test setup: firmware](../generic-test-setup.md#firmware). -## BMA001.001 Boot menu enabling +## BMA001.001 Boot menu enable **Test description** @@ -51,7 +51,7 @@ This test aims to verify that, the boot menu is accessible when the 1. After using the `BOOT MENU KEY` during boot, the boot menu should be displayed. -## BMA002.001 Boot menu disabling +## BMA002.001 Boot menu disable **Test description** diff --git a/docs/unified-test-documentation/dasharo-security/20R-uefi-setup-password.md b/docs/unified-test-documentation/dasharo-security/20R-uefi-setup-password.md index b2acdd65b2..9794f07ebe 100644 --- a/docs/unified-test-documentation/dasharo-security/20R-uefi-setup-password.md +++ b/docs/unified-test-documentation/dasharo-security/20R-uefi-setup-password.md @@ -186,7 +186,7 @@ Password functionality by entering empty password. 1. Password window should not be displayed. 1. The DUT should boot into `Setup Menu`. -## PSW007.001 Attempt to set non-compilant password +## PSW007.001 Attempt to set non-compliant password **Test description** diff --git a/docs/unified-test-documentation/dasharo-stability/01-net-controller-after-coldboot-warmboot-reboot-suspend.md b/docs/unified-test-documentation/dasharo-stability/01-net-controller-after-coldboot-warmboot-reboot-suspend.md index 4e73b3f0f1..3df22a8112 100644 --- a/docs/unified-test-documentation/dasharo-stability/01-net-controller-after-coldboot-warmboot-reboot-suspend.md +++ b/docs/unified-test-documentation/dasharo-stability/01-net-controller-after-coldboot-warmboot-reboot-suspend.md @@ -14,7 +14,7 @@ [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). 1. The `Thunderbolt docking station` connected to the Thunderbolt port. -## NET001.001 201 controller after coldboot (Ubuntu) +## NET001.201 NET controller after coldboot (Ubuntu) **Test description** @@ -91,11 +91,11 @@ is able to connect to the network after coldboot. up ``` -## NET002.201 NET controller after warmboot (Ubuntu) +## NET002.201 Net controller after warmboot (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## NET003.201 NET controller after reboot (Ubuntu) +## NET003.201 Net controller after reboot (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-stability/C01-usb-type-a-devices-detection.md b/docs/unified-test-documentation/dasharo-stability/C01-usb-type-a-devices-detection.md index 70a026acb3..d404320ee1 100644 --- a/docs/unified-test-documentation/dasharo-stability/C01-usb-type-a-devices-detection.md +++ b/docs/unified-test-documentation/dasharo-stability/C01-usb-type-a-devices-detection.md @@ -14,7 +14,7 @@ [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). 1. Connect the `USB device` to the USB Type-A port. -## SUD0001.201 USB devices detection after cold boot (Ubuntu) +## SUD001.201 USB devices detection after cold boot (Ubuntu) **Test description** @@ -62,14 +62,14 @@ iterations. The output of each `lsusb` command should contain an entry of the connected `USB device`. -## SUD0002.201 USB devices detection after warm boot (Ubuntu) +## SUD002.201 USB devices detection after warm boot (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## SUD0003.201 USB devices detection after reboot (Ubuntu) +## SUD003.201 USB devices detection after reboot (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## SUD0004.201 USB devices detection after suspension (Ubuntu) +## SUD004.201 USB devices detection after suspension (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-stability/C02-m2-wi-fi.md b/docs/unified-test-documentation/dasharo-stability/C02-m2-wi-fi.md index 753011204a..0b29041b08 100644 --- a/docs/unified-test-documentation/dasharo-stability/C02-m2-wi-fi.md +++ b/docs/unified-test-documentation/dasharo-stability/C02-m2-wi-fi.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## SMW0001.201 Wi-fi connection after cold boot (Ubuntu) +## SMW001.201 Wi-fi connection after cold boot (Ubuntu) **Test description** @@ -97,14 +97,14 @@ after performing a cold boot. The test should be performed in multiple iteration XX:XX:XX:XX:XX:XX NED-WIFI Infra 11 270 Mbit/s 17 ▂___ WPA2 ``` -## SMW0002.201 Wi-fi connection after warm boot (Ubuntu) +## SMW002.201 Wi-fi connection after warm boot (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## SMW0003.201 Wi-fi connection after reboot (Ubuntu) +## SMW003.201 Wi-fi connection after reboot (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## SMW0004.201 Wi-fi connection after suspension (Ubuntu) +## SMW004.201 Wi-fi connection after suspension (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-stability/C03-nvme-detection.md b/docs/unified-test-documentation/dasharo-stability/C03-nvme-detection.md index 2b6ae7aa1f..631e00fa80 100644 --- a/docs/unified-test-documentation/dasharo-stability/C03-nvme-detection.md +++ b/docs/unified-test-documentation/dasharo-stability/C03-nvme-detection.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## SNV0001.201 NVMe detection after cold boot (Ubuntu) +## SNV001.201 NVMe detection after cold boot (Ubuntu) **Test description** @@ -61,14 +61,14 @@ on the DUT NVMe disk. Example output: 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 980 ``` -## SNV0001.201 NVMe detection after warm boot (Ubuntu) +## SNV002.201 NVMe detection after warm boot (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## SNV0003.201 NVMe detection after reboot (Ubuntu) +## SNV003.201 NVMe detection after reboot (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop -## SNV0004.201 NVMe detection after suspension (Ubuntu) +## SNV004.201 NVMe detection after suspension (Ubuntu) The test is fully automated. Refer to https://github.com/Dasharo/open-source-firmware-validation/tree/develop diff --git a/docs/unified-test-documentation/dasharo-stability/C04-power-management.md b/docs/unified-test-documentation/dasharo-stability/C04-power-management.md index 10eaa014cf..f33716bcb4 100644 --- a/docs/unified-test-documentation/dasharo-stability/C04-power-management.md +++ b/docs/unified-test-documentation/dasharo-stability/C04-power-management.md @@ -13,7 +13,7 @@ 1. Proceed with the [Generic test setup: OS post installation steps](../generic-test-setup.md#post-installation). -## SPM001.001 2x S0ix suspend cycle (Battery) (Ubuntu) +## SPM001.201 2x S0ix suspend cycle (Battery) (Ubuntu) **Test description** @@ -52,7 +52,7 @@ Sleep mode should be entered correctly on each attempt. Waking up should proceed without issues on each attempt. All basic functionality (i.e. builtin keyboard, touchpad, display etc) should keep working. -## SPM001.002 2x S0ix suspend cycle (Battery) (Windows) +## SPM001.301 2x S0ix suspend cycle (Battery) (Windows) **Test description** @@ -91,7 +91,7 @@ Sleep mode should be entered correctly on each attempt. Waking up should proceed without issues on each attempt. All basic functionality (i.e. builtin keyboard, touchpad, display etc) should keep working. -## SPM002.001 2x S0ix suspend cycle (AC) (Ubuntu) +## SPM002.201 2x S0ix suspend cycle (AC) (Ubuntu) **Test description** @@ -130,7 +130,7 @@ Sleep mode should be entered correctly on each attempt. Waking up should proceed without issues on each attempt. All basic functionality (i.e. builtin keyboard, touchpad, display etc) should keep working. -## SPM002.002 2x S0ix suspend cycle (AC) (Windows) +## SPM002.301 2x S0ix suspend cycle (AC) (Windows) **Test description** @@ -169,7 +169,7 @@ Sleep mode should be entered correctly on each attempt. Waking up should proceed without issues on each attempt. All basic functionality (i.e. builtin keyboard, touchpad, display etc) should keep working. -## SPM003.001 2x S3 suspend cycle (Battery) (Ubuntu) +## SPM003.201 2x S3 suspend cycle (Battery) (Ubuntu) **Test description** @@ -208,7 +208,7 @@ Sleep mode should be entered correctly on each attempt. Waking up should proceed without issues on each attempt. All basic functionality (i.e. builtin keyboard, touchpad, display etc) should keep working. -## SPM003.002 2x S3 suspend cycle (Battery) (Windows) +## SPM003.301 2x S3 suspend cycle (Battery) (Windows) **Test description** @@ -247,7 +247,7 @@ Sleep mode should be entered correctly on each attempt. Waking up should proceed without issues on each attempt. All basic functionality (i.e. builtin keyboard, touchpad, display etc) should keep working. -## SPM004.001 2x S3 suspend cycle (AC) (Ubuntu) +## SPM004.201 2x S3 suspend cycle (AC) (Ubuntu) **Test description** @@ -286,7 +286,7 @@ Sleep mode should be entered correctly on each attempt. Waking up should proceed without issues on each attempt. All basic functionality (i.e. builtin keyboard, touchpad, display etc) should keep working. -## SPM004.002 2x S3 suspend cycle (AC) (Windows) +## SPM004.301 2x S3 suspend cycle (AC) (Windows) **Test description** @@ -325,7 +325,7 @@ Sleep mode should be entered correctly on each attempt. Waking up should proceed without issues on each attempt. All basic functionality (i.e. builtin keyboard, touchpad, display etc) should keep working. -## SPM005.001 2x warmboot cycle (Battery) (Ubuntu) +## SPM005.201 2x warmboot cycle (Battery) (Ubuntu) **Test description** @@ -364,7 +364,7 @@ Powering on should proceed without issues on each attempt. All basic functionality (i.e. builtin keyboard, touchpad, display etc) should keep working. -## SPM005.002 2x warmboot cycle (Battery) (Windows) +## SPM005.301 2x warmboot cycle (Battery) (Windows) **Test description** @@ -403,7 +403,7 @@ Powering on should proceed without issues on each attempt. All basic functionality (i.e. builtin keyboard, touchpad, display etc) should keep working. -## SPM006.001 2x warmboot cycle (AC) (Ubuntu) +## SPM006.201 2x warmboot cycle (AC) (Ubuntu) **Test description** @@ -442,7 +442,7 @@ Powering on should proceed without issues on each attempt. All basic functionality (i.e. builtin keyboard, touchpad, display etc) should keep working. -## SPM006.002 2x warmboot cycle (AC) (Windows) +## SPM006.301 2x warmboot cycle (AC) (Windows) **Test description** diff --git a/docs/unified-test-documentation/dasharo-stability/capsule-update.md b/docs/unified-test-documentation/dasharo-stability/capsule-update.md index 89d20075f8..d0753e72c3 100644 --- a/docs/unified-test-documentation/dasharo-stability/capsule-update.md +++ b/docs/unified-test-documentation/dasharo-stability/capsule-update.md @@ -17,7 +17,7 @@ - Serial number (also via `dmidecode`) - BGRT bootsplash logo hash (located in `/sys/firmware/acpi/bgrt`) -## CUP001.001 Capsule Update With Wrong Keys (UEFI Shell) +## CUP001.001 Capsule Update With Wrong Keys **Test description** @@ -57,7 +57,7 @@ instructions given in our --- -## CUP002.001 Capsule Update With Wrong GUID (UEFI Shell) +## CUP002.001 Capsule Update With Wrong GUID **Test description** @@ -208,7 +208,7 @@ instructions given in our --- -## CUP170.001 Verifying UUID (Ubuntu) +## CUP170.201 Verifying UUID (Ubuntu) **Test description** @@ -239,7 +239,7 @@ instructions given in our --- -## CUP180.001 Verifying Serial Number (Ubuntu) +## CUP180.201 Verifying Serial Number (Ubuntu) **Test description** @@ -270,7 +270,7 @@ instructions given in our --- -## CUP190.001 Verifying If Custom Logo Persists Across Updates (Ubuntu) +## CUP190.201 Verifying If Custom Logo Persists Across updates (Ubuntu) **Test description** diff --git a/docs/unified-test-documentation/overview.md b/docs/unified-test-documentation/overview.md index 7c3972be26..2277f72a26 100644 --- a/docs/unified-test-documentation/overview.md +++ b/docs/unified-test-documentation/overview.md @@ -49,7 +49,7 @@ be distinguished: * Fedora 41 * FreeBSD 13.2 * Proxmox VE 7.4 -* OPNsense 23.01 +* OPNSense 23.01 * pfSense CE 2.6.0 `* Unless specified otherwise in the test` diff --git a/docs/unified/protectli/os-installation-opnsense.md b/docs/unified/protectli/os-installation-opnsense.md index 64330f6276..7da7640d06 100644 --- a/docs/unified/protectli/os-installation-opnsense.md +++ b/docs/unified/protectli/os-installation-opnsense.md @@ -1,14 +1,14 @@ -# OPNsense 25.1 installation guide for Protectli Vault series +# OPNSense 25.1 installation guide for Protectli Vault series ## Introduction & installer pre-seed -This document describes preparation and usage of OPNsense Serial Installer -in Dasharo testing environment. For start, an USB stick with OPNsense serial +This document describes preparation and usage of OPNSense Serial Installer +in Dasharo testing environment. For start, an USB stick with OPNSense serial installer is required. All OSFV test IDs and names are referring to the following test suite: ```bash -dasharo-compatibility/os-opnsense.robot +dasharo-compatibility/os-OPNSense.robot ``` ### Installation media preparation @@ -16,7 +16,7 @@ dasharo-compatibility/os-opnsense.robot Such an item may be prepared using `dd` program. Example: ```bash -sudo dd if=~/Downloads/OPNsense-25.1-serial-amd64.img of=/dev/sdX bs=1M status=progress +sudo dd if=~/Downloads/OPNSense-25.1-serial-amd64.img of=/dev/sdX bs=1M status=progress ``` @@ -36,7 +36,7 @@ Label "OPNEFI" is required by test cases OPN001.503. ### Semi-manual bsdinstall modification -Further preparation of OPNsense installation media requires an access to bootable +Further preparation of OPNSense installation media requires an access to bootable FreeBSD-compatible operating system, running on hardware with usable USB port. Following script: [preseed_opnsense.sh](https://github.com/Dasharo/open-source-firmware-validation/blob/develop/scripts/freebsd/preseed_opnsense.sh) @@ -49,19 +49,19 @@ INSTALLER_ROOT_PARTITION, so it points correctly on installer's root partition. ???+ tip FreeBSD-specific command `gpart show` may help with partition identification. -![](../../images/opnsense/opnsense_preseed0.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_preseed0.png){: style="width:480px"} Save eventual changes and execute the script. Verify device name and confirm it with `yes` and `ENTER`. -![](../../images/opnsense/opnsense_preseed1.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_preseed1.png){: style="width:480px"} From now, any modified `bsdinstall` part would be listed and differences would be shown. Accept any change with `yes` and `ENTER`. -![](../../images/opnsense/opnsense_preseed2.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_preseed2.png){: style="width:480px"} -![](../../images/opnsense/opnsense_preseed3.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_preseed3.png){: style="width:480px"} ???+ notice DIFFs on the screenshots are empty, example execution has been done on @@ -69,7 +69,7 @@ shown. Accept any change with `yes` and `ENTER`. Script should exit without any errors: -![](../../images/opnsense/opnsense_preseed4.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_preseed4.png){: style="width:480px"} ???+ success Installation media is now ready for further operation. @@ -80,11 +80,11 @@ With installation media connected to DUT via USB and target drive connected to D via SATA, run following test case: ```bash -OPN001.503 Install operating system on disk (OPNsense) +OPN001.503 Install operating system on disk (OPNSense) ``` and wait for following dialog message: -![](../../images/opnsense/opnsense_serial.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_serial.png){: style="width:480px"} Confirm with `OK`, wait for test suite to finish, and connect to DUT via serial. @@ -94,54 +94,54 @@ You should be asked for installer credentials. Log in with: ```bash login: installer -Password: opnsense +Password: OPNSense ``` -![](../../images/opnsense/opnsense_installer_login.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_installer_login.png){: style="width:480px"} Now select keymap, or navigate to `Select` and confirm default with `ENTER`. -![](../../images/opnsense/opnsense_keymap.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_keymap.png){: style="width:480px"} To begin installation, select `Install (ZFS)`, navigate to `OK` and press `ENTER`. -![](../../images/opnsense/opnsense_zfs1.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_zfs1.png){: style="width:480px"} Now, the ZFS pool name question may appear: -![](../../images/opnsense/opnsense_pool.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_pool.png){: style="width:480px"} Confirm with `ENTER`. Choose `stripe`, navigate to `OK` and press `ENTER`. -![](../../images/opnsense/opnsense_zfs2.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_zfs2.png){: style="width:480px"} Mark `ada0` drive (this is first SATA drive) using `SPACE`, navigate to `OK` using `TAB` and press `ENTER`: -![](../../images/opnsense/opnsense_zfs3.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_zfs3.png){: style="width:480px"} ???+ warning Select installation target drive carefully. You will be asked for confirmation once again, right now. -![](../../images/opnsense/opnsense_zfs4.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_zfs4.png){: style="width:480px"} Installation now begins. -![](../../images/opnsense/opnsense_installation.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_installation.png){: style="width:480px"} After installation finished, navigate to `Complete Install` and press `ENTER`. -![](../../images/opnsense/opnsense_exit.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_exit.png){: style="width:480px"} On next screen, select `Halt now` and press `ENTER`. -![](../../images/opnsense/opnsense_power.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_power.png){: style="width:480px"} ???+ success - OPNsense installation is now finished. Testing environment will be able to boot + OPNSense installation is now finished. Testing environment will be able to boot this by OS searching for `OPNBOOT` ESP partition. ## Testing @@ -150,7 +150,7 @@ To verify testing readiness of finished installation, OS boot test may be execut Run: ```bash -OPN002.503 Boot operating system from disk (OPNsense) +OPN002.503 Boot operating system from disk (OPNSense) ``` -![](../../images/opnsense/opnsense_test.png){: style="width:480px"} +![](../../images/OPNSense/opnsense_test.png){: style="width:480px"} diff --git a/docs/unified/protectli/os-installation.md b/docs/unified/protectli/os-installation.md index 6c0c49f616..289ea730ed 100644 --- a/docs/unified/protectli/os-installation.md +++ b/docs/unified/protectli/os-installation.md @@ -72,19 +72,19 @@ Official documentation can be found Installer images can be downloaded from the official [website](https://proxmox.com/en/downloads/proxmox-virtual-environment/iso). -## OPNsense +## OPNSense ### Installation documentation Official documentation can be found -[here](https://docs.opnsense.org/manual/install.html). +[here](https://docs.OPNSense.org/manual/install.html). -[Dasharo OPNsense 25.1 installation guide](./os-installation-opnsense.md) +[Dasharo OPNSense 25.1 installation guide](./os-installation-OPNSense.md) ### Installation images Installer images can be downloaded from the official -[website](https://opnsense.org/download/). +[website](https://OPNSense.org/download/). ## XCP-NG diff --git a/docs/unified/protectli/test-matrix.md b/docs/unified/protectli/test-matrix.md index f0dc111fee..3a1427abcd 100644 --- a/docs/unified/protectli/test-matrix.md +++ b/docs/unified/protectli/test-matrix.md @@ -92,7 +92,7 @@ subjected from before the release of the new binary. [UDT]: ../../unified-test-documentation/dasharo-compatibility/31O-usb-detect.md [UBT]: ../../unified-test-documentation/dasharo-compatibility/31N-usb-boot.md [PFS]: ../../unified-test-documentation/dasharo-compatibility/341-pfSense-support.md - [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md + [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNSense-support.md [PVE]: ../../unified-test-documentation/dasharo-compatibility/348-proxmox-support.md [USS]: ../../unified-test-documentation/dasharo-compatibility/349-ubuntu-server-support.md @@ -124,8 +124,8 @@ subjected from before the release of the new binary. [BFB]: ../../unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md [BPM]: ../../unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md [BUS]: ../../unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md - [BOS]: ../../unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md - [BOV]: ../../unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md + [BOS]: ../../unified-test-documentation/dasharo-performance/412-OPNSense-serial-booting-performance-test.md + [BOV]: ../../unified-test-documentation/dasharo-performance/413-OPNSense-vga-booting-performance-test.md [BPS]: ../../unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md [BPV]: ../../unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md @@ -157,7 +157,7 @@ subjected from before the release of the new binary. | 20. | [USB detection][UDT] | UDT | All | | 21. | [USB booting][UBT] | UBT | All | | 22. | [pfSense support][PFS] | PFS | All | - | 23. | [OPNsense support][OPN] | OPN | All | + | 23. | [OPNSense support][OPN] | OPN | All | | 24. | [Proxmox support][PVE] | PVE | All | | 25. | [Ubuntu Server support][USS] | USS | All | @@ -184,7 +184,7 @@ subjected from before the release of the new binary. [UDT]: ../../unified-test-documentation/dasharo-compatibility/31O-usb-detect.md [UBT]: ../../unified-test-documentation/dasharo-compatibility/31N-usb-boot.md [PFS]: ../../unified-test-documentation/dasharo-compatibility/341-pfSense-support.md - [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md + [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNSense-support.md [PVE]: ../../unified-test-documentation/dasharo-compatibility/348-proxmox-support.md [USS]: ../../unified-test-documentation/dasharo-compatibility/349-ubuntu-server-support.md @@ -227,8 +227,8 @@ subjected from before the release of the new binary. | 7. | [FreeBSD booting performance test][BFB] | BFB | All | | 8. | [Proxmox booting performance test][BPM] | BPM | All | | 9. | [Ubuntu Server booting performance test][BUS] | BUS | All | - | 10. | [OPNsense (serial output) booting performance test][BOS] | BOS | All | - | 11. | [OPNsense (VGA output) booting performance test][BOV] | BOV | All | + | 10. | [OPNSense (serial output) booting performance test][BOS] | BOS | All | + | 11. | [OPNSense (VGA output) booting performance test][BOV] | BOV | All | | 12. | [pfSense (serial output) booting performance test][BPS] | BPS | All | | 13. | [pfSense (VGA output) booting performance test][BPV] | BPV | All | @@ -241,8 +241,8 @@ subjected from before the release of the new binary. [BFB]: ../../unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md [BPM]: ../../unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md [BUS]: ../../unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md - [BOS]: ../../unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md - [BOV]: ../../unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md + [BOS]: ../../unified-test-documentation/dasharo-performance/412-OPNSense-serial-booting-performance-test.md + [BOV]: ../../unified-test-documentation/dasharo-performance/413-OPNSense-vga-booting-performance-test.md [BPS]: ../../unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md [BPV]: ../../unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md @@ -272,7 +272,7 @@ subjected from before the release of the new binary. | 20. | [USB detection][UDT] | UDT | All | | 21. | [USB booting][UBT] | UBT | All | | 22. | [pfSense support][PFS] | PFS | All | - | 23. | [OPNsense support][OPN] | OPN | All | + | 23. | [OPNSense support][OPN] | OPN | All | | 24. | [Proxmox support][PVE] | PVE | All | | 25. | [Ubuntu Server support][USS] | USS | All | @@ -297,7 +297,7 @@ subjected from before the release of the new binary. [UDT]: ../../unified-test-documentation/dasharo-compatibility/31O-usb-detect.md [UBT]: ../../unified-test-documentation/dasharo-compatibility/31N-usb-boot.md [PFS]: ../../unified-test-documentation/dasharo-compatibility/341-pfSense-support.md - [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md + [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNSense-support.md [PVE]: ../../unified-test-documentation/dasharo-compatibility/348-proxmox-support.md [USS]: ../../unified-test-documentation/dasharo-compatibility/349-ubuntu-server-support.md @@ -339,8 +339,8 @@ subjected from before the release of the new binary. | 7. | [FreeBSD booting performance test][BFB] | BFB | All | | 8. | [Proxmox booting performance test][BPM] | BPM | All | | 9. | [Ubuntu Server booting performance test][BUS] | BUS | All | - | 10. | [OPNsense (serial output) booting performance test][BOS] | BOS | All | - | 11. | [OPNsense (VGA output) booting performance test][BOV] | BOV | All | + | 10. | [OPNSense (serial output) booting performance test][BOS] | BOS | All | + | 11. | [OPNSense (VGA output) booting performance test][BOV] | BOV | All | | 12. | [pfSense (serial output) booting performance test][BPS] | BPS | All | | 13. | [pfSense (VGA output) booting performance test][BPV] | BPV | All | @@ -353,8 +353,8 @@ subjected from before the release of the new binary. [BFB]: ../../unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md [BPM]: ../../unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md [BUS]: ../../unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md - [BOS]: ../../unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md - [BOV]: ../../unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md + [BOS]: ../../unified-test-documentation/dasharo-performance/412-OPNSense-serial-booting-performance-test.md + [BOV]: ../../unified-test-documentation/dasharo-performance/413-OPNSense-vga-booting-performance-test.md [BPS]: ../../unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md [BPV]: ../../unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md @@ -465,7 +465,7 @@ subjected from before the release of the new binary. | 19. | [USB detection][UDT] | UDT | All | | 20. | [USB booting][UBT] | UBT | All | | 21. | [pfSense support][PFS] | PFS | All | - | 22. | [OPNsense support][OPN] | OPN | All | + | 22. | [OPNSense support][OPN] | OPN | All | | 23. | [Proxmox support][PVE] | PVE | All | | 24. | [Ubuntu Server support][USS] | USS | All | @@ -492,7 +492,7 @@ subjected from before the release of the new binary. [UDT]: ../../unified-test-documentation/dasharo-compatibility/31O-usb-detect.md [UBT]: ../../unified-test-documentation/dasharo-compatibility/31N-usb-boot.md [PFS]: ../../unified-test-documentation/dasharo-compatibility/341-pfSense-support.md - [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md + [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNSense-support.md [PVE]: ../../unified-test-documentation/dasharo-compatibility/348-proxmox-support.md [USS]: ../../unified-test-documentation/dasharo-compatibility/349-ubuntu-server-support.md @@ -529,8 +529,8 @@ subjected from before the release of the new binary. | 7. | [FreeBSD booting performance test][BFB] | BFB | All | | 8. | [Proxmox booting performance test][BPM] | BPM | All | | 9. | [Ubuntu Server booting performance test][BUS] | BUS | All | - | 10. | [OPNsense (serial output) booting performance test][BOS] | BOS | All | - | 11. | [OPNsense (VGA output) booting performance test][BOV] | BOV | All | + | 10. | [OPNSense (serial output) booting performance test][BOS] | BOS | All | + | 11. | [OPNSense (VGA output) booting performance test][BOV] | BOV | All | | 12. | [pfSense (serial output) booting performance test][BPS] | BPS | All | | 13. | [pfSense (VGA output) booting performance test][BPV] | BPV | All | @@ -543,8 +543,8 @@ subjected from before the release of the new binary. [BFB]: ../../unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md [BPM]: ../../unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md [BUS]: ../../unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md - [BOS]: ../../unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md - [BOV]: ../../unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md + [BOS]: ../../unified-test-documentation/dasharo-performance/412-OPNSense-serial-booting-performance-test.md + [BOV]: ../../unified-test-documentation/dasharo-performance/413-OPNSense-vga-booting-performance-test.md [BPS]: ../../unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md [BPV]: ../../unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md @@ -573,7 +573,7 @@ subjected from before the release of the new binary. | 20. | [USB detection][UDT] | UDT | All | | 21. | [USB booting][UBT] | UBT | All | | 22. | [pfSense support][PFS] | PFS | All | - | 23. | [OPNsense support][OPN] | OPN | All | + | 23. | [OPNSense support][OPN] | OPN | All | | 24. | [Proxmox support][PVE] | PVE | All | | 25. | [Ubuntu Server support][USS] | USS | All | | 26. | [Auto boot time-out][BMM] | BMM | All | @@ -605,7 +605,7 @@ subjected from before the release of the new binary. [UDT]: ../../unified-test-documentation/dasharo-compatibility/31O-usb-detect.md [UBT]: ../../unified-test-documentation/dasharo-compatibility/31N-usb-boot.md [PFS]: ../../unified-test-documentation/dasharo-compatibility/341-pfSense-support.md - [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md + [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNSense-support.md [PVE]: ../../unified-test-documentation/dasharo-compatibility/348-proxmox-support.md [USS]: ../../unified-test-documentation/dasharo-compatibility/349-ubuntu-server-support.md [CPU]: ../../unified-test-documentation/dasharo-compatibility/31T-cpu-status.md @@ -656,8 +656,8 @@ subjected from before the release of the new binary. | 7. | [FreeBSD booting performance test][BFB] | BFB | All | | 8. | [Proxmox booting performance test][BPM] | BPM | All | | 9. | [Ubuntu Server booting performance test][BUS] | BUS | All | - | 10. | [OPNsense (serial output) booting performance test][BOS] | BOS | All | - | 11. | [OPNsense (VGA output) booting performance test][BOV] | BOV | All | + | 10. | [OPNSense (serial output) booting performance test][BOS] | BOS | All | + | 11. | [OPNSense (VGA output) booting performance test][BOV] | BOV | All | | 12. | [pfSense (serial output) booting performance test][BPS] | BPS | All | | 13. | [pfSense (VGA output) booting performance test][BPV] | BPV | All | @@ -670,8 +670,8 @@ subjected from before the release of the new binary. [BFB]: ../../unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md [BPM]: ../../unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md [BUS]: ../../unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md - [BOS]: ../../unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md - [BOV]: ../../unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md + [BOS]: ../../unified-test-documentation/dasharo-performance/412-OPNSense-serial-booting-performance-test.md + [BOV]: ../../unified-test-documentation/dasharo-performance/413-OPNSense-vga-booting-performance-test.md [BPS]: ../../unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md [BPV]: ../../unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md @@ -701,7 +701,7 @@ subjected from before the release of the new binary. | 20. | [USB detection][UDT] | UDT | All | | 21. | [USB booting][UBT] | UBT | All | | 22. | [pfSense support][PFS] | PFS | All | - | 23. | [OPNsense support][OPN] | OPN | All | + | 23. | [OPNSense support][OPN] | OPN | All | | 24. | [Proxmox support][PVE] | PVE | All | | 25. | [Ubuntu Server support][USS] | USS | All | @@ -726,7 +726,7 @@ subjected from before the release of the new binary. [UDT]: ../../unified-test-documentation/dasharo-compatibility/31O-usb-detect.md [UBT]: ../../unified-test-documentation/dasharo-compatibility/31N-usb-boot.md [PFS]: ../../unified-test-documentation/dasharo-compatibility/341-pfSense-support.md - [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md + [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNSense-support.md [PVE]: ../../unified-test-documentation/dasharo-compatibility/348-proxmox-support.md [USS]: ../../unified-test-documentation/dasharo-compatibility/349-ubuntu-server-support.md @@ -768,8 +768,8 @@ subjected from before the release of the new binary. | 7. | [FreeBSD booting performance test][BFB] | BFB | All | | 8. | [Proxmox booting performance test][BPM] | BPM | All | | 9. | [Ubuntu Server booting performance test][BUS] | BUS | All | - | 10. | [OPNsense (serial output) booting performance test][BOS] | BOS | All | - | 11. | [OPNsense (VGA output) booting performance test][BOV] | BOV | All | + | 10. | [OPNSense (serial output) booting performance test][BOS] | BOS | All | + | 11. | [OPNSense (VGA output) booting performance test][BOV] | BOV | All | | 12. | [pfSense (serial output) booting performance test][BPS] | BPS | All | | 13. | [pfSense (VGA output) booting performance test][BPV] | BPV | All | @@ -782,8 +782,8 @@ subjected from before the release of the new binary. [BFB]: ../../unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md [BPM]: ../../unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md [BUS]: ../../unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md - [BOS]: ../../unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md - [BOV]: ../../unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md + [BOS]: ../../unified-test-documentation/dasharo-performance/412-OPNSense-serial-booting-performance-test.md + [BOV]: ../../unified-test-documentation/dasharo-performance/413-OPNSense-vga-booting-performance-test.md [BPS]: ../../unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md [BPV]: ../../unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md @@ -812,7 +812,7 @@ subjected from before the release of the new binary. | 20. | [USB detection][UDT] | UDT | All | | 21. | [USB booting][UBT] | UBT | All | | 22. | [pfSense support][PFS] | PFS | All | - | 23. | [OPNsense support][OPN] | OPN | All | + | 23. | [OPNSense support][OPN] | OPN | All | | 24. | [Proxmox support][PVE] | PVE | All | | 25. | [Ubuntu Server support][USS] | USS | All | | 26. | [Auto boot time-out][BMM] | BMM | All | @@ -844,7 +844,7 @@ subjected from before the release of the new binary. [UDT]: ../../unified-test-documentation/dasharo-compatibility/31O-usb-detect.md [UBT]: ../../unified-test-documentation/dasharo-compatibility/31N-usb-boot.md [PFS]: ../../unified-test-documentation/dasharo-compatibility/341-pfSense-support.md - [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md + [OPN]: ../../unified-test-documentation/dasharo-compatibility/342-OPNSense-support.md [PVE]: ../../unified-test-documentation/dasharo-compatibility/348-proxmox-support.md [USS]: ../../unified-test-documentation/dasharo-compatibility/349-ubuntu-server-support.md [CPU]: ../../unified-test-documentation/dasharo-compatibility/31T-cpu-status.md @@ -895,8 +895,8 @@ subjected from before the release of the new binary. | 7. | [FreeBSD booting performance test][BFB] | BFB | All | | 8. | [Proxmox booting performance test][BPM] | BPM | All | | 9. | [Ubuntu Server booting performance test][BUS] | BUS | All | - | 10. | [OPNsense (serial output) booting performance test][BOS] | BOS | All | - | 11. | [OPNsense (VGA output) booting performance test][BOV] | BOV | All | + | 10. | [OPNSense (serial output) booting performance test][BOS] | BOS | All | + | 11. | [OPNSense (VGA output) booting performance test][BOV] | BOV | All | | 12. | [pfSense (serial output) booting performance test][BPS] | BPS | All | | 13. | [pfSense (VGA output) booting performance test][BPV] | BPV | All | @@ -909,7 +909,7 @@ subjected from before the release of the new binary. [BFB]: ../../unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md [BPM]: ../../unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md [BUS]: ../../unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md - [BOS]: ../../unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md - [BOV]: ../../unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md + [BOS]: ../../unified-test-documentation/dasharo-performance/412-OPNSense-serial-booting-performance-test.md + [BOV]: ../../unified-test-documentation/dasharo-performance/413-OPNSense-vga-booting-performance-test.md [BPS]: ../../unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md [BPV]: ../../unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md diff --git a/docs/variants/firewall.md b/docs/variants/firewall.md index 9a92a29979..38926754d8 100644 --- a/docs/variants/firewall.md +++ b/docs/variants/firewall.md @@ -13,7 +13,7 @@ constant support, maintenance and transparency. For whom: For people who look for a secure firewall solution based on open-source software and technologies. TBD: we need more precise characteristics of Dasharo Firewall, it should be -defined by tests we applying to typical firewall devices e.g. OPNsense +defined by tests we applying to typical firewall devices e.g. OPNSense compatibility. TBD: maybe also add some picture/diagram of Dasharo Firewall to compliment the text. diff --git a/docs/variants/pc_engines/overview.md b/docs/variants/pc_engines/overview.md index 79d52d7707..c08c4929b3 100644 --- a/docs/variants/pc_engines/overview.md +++ b/docs/variants/pc_engines/overview.md @@ -21,7 +21,7 @@ PC Engines is a well-recognized brand in the open-source community mostly because of full [schematics availability (apu2d example)](https://www.pcengines.ch/schema/apu2d.pdf) and use of [open-source firmware](https://pcengines.github.io/). PC Engines products are top-rated -among pfSense and OPNsense users. What you can see based on the number of forum +among pfSense and OPNSense users. What you can see based on the number of forum topics regarding apu platforms. ## Status diff --git a/docs/variants/protectli_vp2420/releases.md b/docs/variants/protectli_vp2420/releases.md index 239c658f4d..bc87b3615d 100644 --- a/docs/variants/protectli_vp2420/releases.md +++ b/docs/variants/protectli_vp2420/releases.md @@ -201,7 +201,7 @@ using [this key](https://raw.githubusercontent.com/3mdeb/3mdeb-secpack/master/cu - [Dasharo BIOS lock menu is missing](https://github.com/Dasharo/dasharo-issues/issues/291) - [iPXE entry doesn't occur in setup menu](https://github.com/Dasharo/dasharo-issues/issues/289) -- [Impossibility of pfSense/OPNsense console versions installation](https://github.com/Dasharo/dasharo-issues/issues/289) +- [Impossibility of pfSense/OPNSense console versions installation](https://github.com/Dasharo/dasharo-issues/issues/289) ### Known issues diff --git a/mkdocs.yml b/mkdocs.yml index cf842b5de4..b12e8c0334 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -650,7 +650,7 @@ nav: - '[NBT] Network boot utilities': unified-test-documentation/dasharo-compatibility/315b-netboot-utilities.md - '[NVI] NVIDIA Graphics support': unified-test-documentation/dasharo-compatibility/319-nvidia-graphics.md - '[NVM] NVME support': unified-test-documentation/dasharo-compatibility/312-nvme-support.md - - '[OPN] OPNsense support': unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md + - '[OPN] OPNSense support': unified-test-documentation/dasharo-compatibility/342-OPNSense-support.md - '[PBT] Petitboot payload support': unified-test-documentation/dasharo-compatibility/31V-petitboot-payload-support.md - '[PEX] PCI Express ports support': unified-test-documentation/dasharo-compatibility/31R-pcie-ports.md - '[PFS] pfSense support': unified-test-documentation/dasharo-compatibility/341-pfSense-support.md @@ -697,8 +697,8 @@ nav: #pre-commit-sort-start - '[BDE] Debian booting performance test': unified-test-documentation/dasharo-performance/408-debian-booting-performance-test.md - '[BFB] FreeBSD booting performance test': unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md - - '[BOS] OPNsense (serial output) booting performance test': unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md - - '[BOV] OPNsense (VGA output) booting performance test': unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md + - '[BOS] OPNSense (serial output) booting performance test': unified-test-documentation/dasharo-performance/412-OPNSense-serial-booting-performance-test.md + - '[BOV] OPNSense (VGA output) booting performance test': unified-test-documentation/dasharo-performance/413-OPNSense-vga-booting-performance-test.md - '[BPM] Proxmox booting performance test': unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md - '[BPS] pfSense (serial output) booting performance test': unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md - '[BPV] pfSense (VGA output) booting performance test': unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md