diff --git a/docs/transparent-validation/rte/v1.1.0/specification.md b/docs/transparent-validation/rte/v1.1.0/specification.md index 4b091f31bb5..37179f2509c 100644 --- a/docs/transparent-validation/rte/v1.1.0/specification.md +++ b/docs/transparent-validation/rte/v1.1.0/specification.md @@ -51,7 +51,7 @@ operating system and starts automatically on port `8000` without the necessity of additional configuration. REST API dashboard can be reached through the Internet browser and provides a possibility to: -* control Device Under Test power supply (coldboot and warmboot) +* control Device Under Test power supply (cold boot and warm boot) * reset Device Under Test platform * flash Device Under Test firmware More information can be found at [RteCtrl repository](https://github.com/3mdeb/RteCtrl) 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 7e7324e76cb..b9956630125 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 @@ -1560,11 +1560,11 @@ properly by the operating system. 1. Pressing the button once should increase the keyboard backlight. -## ECR025.001 Permanent keyboard illumination after cold-boot (Firmware) +## ECR025.001 Permanent keyboard illumination after cold boot (Firmware) **Test description** -This test aims to verify that after performing cold-boot, keyboard still +This test aims to verify that after performing cold boot, keyboard still illuminates in firmware. **Test configuration data** @@ -1587,13 +1587,13 @@ illuminates in firmware. **Expected result** -1. After cold-boot keyboard brightness and colors settings remain the same. +1. After cold boot keyboard brightness and colors settings remain the same. -## ECR025.002 Permanent keyboard illumination after cold-boot (Ubuntu 22.04) +## ECR025.002 Permanent keyboard illumination after cold boot (Ubuntu 22.04) **Test description** -This test aims to verify that after performing cold-boot, keyboard still +This test aims to verify that after performing cold boot, keyboard still illuminates in Ubuntu 22.04. **Test configuration data** @@ -1620,13 +1620,13 @@ illuminates in Ubuntu 22.04. **Expected result** -1. After cold-boot keyboard brightness and colors settings remain the same. +1. After cold boot keyboard brightness and colors settings remain the same. -## ECR025.003 Permanent keyboard illumination after cold-boot (Windows 11) +## ECR025.003 Permanent keyboard illumination after cold boot (Windows 11) **Test description** -This test aims to verify that after performing cold-boot, keyboard still +This test aims to verify that after performing cold boot, keyboard still illuminates in Windows 11. **Test configuration data** @@ -1653,13 +1653,13 @@ illuminates in Windows 11. **Expected result** -1. After cold-boot keyboard brightness and colors settings remain the same. +1. After cold boot keyboard brightness and colors settings remain the same. -## ECR026.001 Permanent keyboard illumination after warm-boot (Firmware) +## ECR026.001 Permanent keyboard illumination after warm boot (Firmware) **Test description** -This test aims to verify that after performing warm-boot, keyboard still +This test aims to verify that after performing warm boot, keyboard still illuminates in firmware. **Test configuration data** @@ -1681,13 +1681,13 @@ illuminates in firmware. **Expected result** -1. After warm-boot keyboard brightness and colors settings remain the same. +1. After warm boot keyboard brightness and colors settings remain the same. -## ECR026.002 Permanent keyboard illumination after warm-boot (Ubuntu 22.04) +## ECR026.002 Permanent keyboard illumination after warm boot (Ubuntu 22.04) **Test description** -This test aims to verify that after performing warm-boot, keyboard still +This test aims to verify that after performing warm boot, keyboard still illuminates in Ubuntu 22.04. **Test configuration data** @@ -1713,13 +1713,13 @@ illuminates in Ubuntu 22.04. **Expected result** -1. After warm-boot keyboard brightness and colors settings remain the same. +1. After warm boot keyboard brightness and colors settings remain the same. -## ECR026.003 Permanent keyboard illumination after warm-boot (Windows 11) +## ECR026.003 Permanent keyboard illumination after warm boot (Windows 11) **Test description** -This test aims to verify that after performing warm-boot, keyboard still +This test aims to verify that after performing warm boot, keyboard still illuminates in Windows 11. **Test configuration data** @@ -1745,7 +1745,7 @@ illuminates in Windows 11. **Expected result** -1. After warm-boot keyboard brightness and colors settings remain the same. +1. After warm boot keyboard brightness and colors settings remain the same. ## ECR027.001 Permanent keyboard illumination after reboot (Firmware) diff --git a/docs/unified-test-documentation/dasharo-compatibility/31N-usb-boot.md b/docs/unified-test-documentation/dasharo-compatibility/31N-usb-boot.md index 4d52d8d4229..c5ffcc421ea 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31N-usb-boot.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31N-usb-boot.md @@ -1,11 +1,11 @@ # Dasharo Compatibility: USB Boot -## UBT001.001 USB detect and boot after coldboot +## UBT001.001 USB detect and boot after cold boot **Test description** This test aims to verify that the DUT properly detects USB device and boots -into the operating system after coldboot (reboot realized by power supply +into the operating system after cold boot (reboot realized by power supply cutting off then restoring back). This test case may be re-done several times to specify the platform and connection stability. @@ -32,14 +32,14 @@ to specify the platform and connection stability. **Expected result** The `Debian GNU/Linux` is visible and confirms successful boot into OS after -coldboot. +cold boot. -## UBT002.001 USB detect and boot after warmboot +## UBT002.001 USB detect and boot after warm boot **Test description** This test aims to verify that the DUT properly detects USB device and boots -into the operating system after warmboot (reboot realized by device turning +into the operating system after warm boot (reboot realized by device turning off then turning on). This test case may be re-done several times to specify the platform and connection stability. @@ -65,7 +65,7 @@ the platform and connection stability. **Expected result** The `Debian GNU/Linux` is visible and confirms successful boot into OS after -warmboot. +warm boot. ## UBT003.001 USB detect and boot after system reboot diff --git a/docs/unified-test-documentation/dasharo-compatibility/31O-usb-detect.md b/docs/unified-test-documentation/dasharo-compatibility/31O-usb-detect.md index 4ae29305db0..13dbe02a9fe 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/31O-usb-detect.md +++ b/docs/unified-test-documentation/dasharo-compatibility/31O-usb-detect.md @@ -1,11 +1,11 @@ # Dasharo Compatibility: USB Detection -## UDT001.001 USB detection after coldboot +## UDT001.001 USB detection after cold boot **Test description** This test aims to verify that the DUT properly detects USB device after -coldboot (reboot realized by power supply cutting off then restoring back). +cold boot (reboot realized by power supply cutting off then restoring back). This test case may be re-done several times to specify the platform and connection stability. @@ -30,15 +30,16 @@ connection stability. **Expected result** The `USB_STICK` entry is visible which confirms successful detection after -coldboot. +cold boot. -## UDT002.001 USB detection after warmboot +## UDT002.001 USB detection after warm boot **Test description** This test aims to verify that the DUT properly detects USB device after -warmboot (reboot realized by device turning off then turning on). This test case -may be re-done several times to specify the platform and connection stability. +warm boot (reboot realized by device turning off then turning on). This test +case may be re-done several times to specify the platform and connection +stability. **Test configuration data** @@ -60,7 +61,7 @@ may be re-done several times to specify the platform and connection stability. **Expected result** The `USB_STICK` entry is visible which confirms successful detection after -warmboot. +warm boot. ## UDT003.001 USB detection after system reboot diff --git a/docs/unified-test-documentation/dasharo-compatibility/323-docking-station-detect.md b/docs/unified-test-documentation/dasharo-compatibility/323-docking-station-detect.md index 09b8b9d9042..841c3c5b27d 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/323-docking-station-detect.md +++ b/docs/unified-test-documentation/dasharo-compatibility/323-docking-station-detect.md @@ -14,12 +14,12 @@ [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). 1. The `USB-C docking station` connected to the USB-C port. -## DUD001.001 Docking station detection after coldboot (Ubuntu 22.04) +## DUD001.001 Docking station detection after cold boot (Ubuntu 22.04) **Test description** This test aims to verify that the DUT properly detects the docking station after -coldboot (realized by power supply cutting off then restoring back). +cold boot (realized by power supply cutting off then restoring back). This test case may be re-done several times to specify the platform and connection stability. @@ -60,12 +60,12 @@ Bus 002 Device 009: Prolific Technology, Inc. USB SD Card Reader Bus 002 Device 008: VIA Labs, Inc. USB3.0 Hub ``` -## DUD002.001 Docking station detection after warmboot (Ubuntu 22.04) +## DUD002.001 Docking station detection after warm boot (Ubuntu 22.04) **Test description** This test aims to verify that the DUT properly detects the docking station -after warmboot (realized by device turning off then turning on). This test case +after warm boot (realized by device turning off then turning on). This test case may be re-done several times to specify the platform and connection stability. **Test configuration data** diff --git a/docs/unified-test-documentation/dasharo-compatibility/352-thunderbolt-docking-station-detect.md b/docs/unified-test-documentation/dasharo-compatibility/352-thunderbolt-docking-station-detect.md index 614e26a81e3..fc3fd7e591e 100644 --- a/docs/unified-test-documentation/dasharo-compatibility/352-thunderbolt-docking-station-detect.md +++ b/docs/unified-test-documentation/dasharo-compatibility/352-thunderbolt-docking-station-detect.md @@ -14,12 +14,12 @@ [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). 1. The `Thunderbolt docking station` connected to the Thunderbolt port. -## TDD001.001 Docking station detection after coldboot (Ubuntu 22.04) +## TDD001.001 Docking station detection after cold boot (Ubuntu 22.04) **Test description** This test aims to verify that the DUT properly detects the docking station after -coldboot (realized by power supply cutting off then restoring back). +cold boot (realized by power supply cutting off then restoring back). This test case may be re-done several times to specify the platform and connection stability. @@ -60,12 +60,12 @@ Bus 002 Device 009: Prolific Technology, Inc. USB SD Card Reader Bus 002 Device 008: VIA Labs, Inc. USB3.0 Hub ``` -## TDD002.001 Docking station detection after warmboot (Ubuntu 22.04) +## TDD002.001 Docking station detection after warm boot (Ubuntu 22.04) **Test description** This test aims to verify that the DUT properly detects the docking station -after warmboot (realized by device turning off then turning on). This test case +after warm boot (realized by device turning off then turning on). This test case may be re-done several times to specify the platform and connection stability. **Test configuration data** 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 c0d1a2aacac..68e237b807f 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 @@ -13,11 +13,11 @@ 1. Download `cbmem` from to the DUT. -## CBMEM001.001 coreboot booting time measure after coldboot (Ubuntu 22.04) +## CBMEM001.001 coreboot booting time measure after cold boot (Ubuntu 22.04) **Test description** -This test aims to verify whether the DUT boots after coldboot and how long this +This test aims to verify whether the DUT boots after cold boot 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. @@ -44,11 +44,11 @@ sudo ./cbmem -T The output of the command should contain the information about duration of all boot stages. -## CBMEM002.001 coreboot booting time measure after warmboot (Ubuntu 22.04) +## CBMEM002.001 coreboot booting time measure after warm boot (Ubuntu 22.04) **Test description** -This test aims to verify whether the DUT boots after warmboot and how long this +This test aims to verify whether the DUT boots after warm boot 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. 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 73873d5c2f3..834e5d58e53 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 @@ -13,11 +13,11 @@ 1. Proceed with the [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). -## DBM001.001 Device boot measure after coldboot (Ubuntu 22.04) +## DBM001.001 Device boot measure after cold boot (Ubuntu 22.04) **Test description** -This test aims to verify whether the DUT boots after coldboot and how long this +This test aims to verify whether the DUT boots after cold boot 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. @@ -50,11 +50,11 @@ results and specify the platform stability. The output of the command should contain the information about duration of all boot stages. -## DBM002.001 Device boot measure after warmboot (Ubuntu 22.04) +## DBM002.001 Device boot measure after warm boot (Ubuntu 22.04) **Test description** -This test aims to verify whether the DUT boots after warmboot and how long this +This test aims to verify whether the DUT boots after warm boot 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. 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 113f1ecc135..f863da2bd13 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,12 +19,12 @@ apt-get install --assume-yes lm-sensors ``` -## FNM001.001 Fan does not stuck after coldboot (Ubuntu 22.04) +## FNM001.001 Fan does not stuck after cold boot (Ubuntu 22.04) **Test description** This test aims to verify that the fan does not stuck on initial or any defined -speed after coldboot. +speed after cold boot. **Test configuration data** @@ -64,12 +64,12 @@ Example output: fan1: 1131 RPM (min = 329 RPM) ``` -## FNM002.001 Fan does not stuck after warmboot (Ubuntu 22.04) +## FNM002.001 Fan does not stuck after warm boot (Ubuntu 22.04) **Test description** This test aims to verify that the fan does not stuck on initial or any defined -speed after warmboot. +speed after warm boot. **Test configuration data** 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 4ec66fea256..f898a541b8c 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,12 +13,12 @@ 1. Proceed with the [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). -## BUB001.001 Boot Ubuntu LTS from disk after cold-boot +## BUB001.001 Boot Ubuntu LTS from disk after cold boot **Test description** This test aims to verify that Ubuntu LTS could be booted from the disk on the -DUT after cold-boot. The test is performed in multiple iterations. +DUT after cold boot. The test is performed in multiple iterations. **Test configuration data** @@ -43,12 +43,12 @@ 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.001 Boot Ubuntu LTS from disk after warm boot **Test description** This test aims to verify that Ubuntu LTS could be booted from the disk on the -DUT after warm-boot. The test is performed in multiple iterations. +DUT after warm boot. The test is performed in multiple iterations. **Test configuration data** 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 238a2c3907d..d00798803f2 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,12 +13,12 @@ 1. Proceed with the [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). -## BDE001.001 Boot Debian LTS from disk after cold-boot +## BDE001.001 Boot Debian LTS from disk after cold boot **Test description** This test aims to verify that Debian LTS could be booted from the disk -on the DUT after cold-boot. The test is performed in multiple iterations. +on the DUT after cold boot. The test is performed in multiple iterations. **Test configuration data** @@ -43,12 +43,12 @@ 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.001 Boot Debian LTS from disk after warm boot **Test description** This test aims to verify that Debian LTS could be booted from the disk -on the DUT after warm-boot. The test is performed in multiple iterations. +on the DUT after warm boot. The test is performed in multiple iterations. **Test configuration data** 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 0beb7aa2f32..70ba904241f 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,12 +13,12 @@ 1. Proceed with the [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). -## BFB001.001 Boot FreeBSD-RELEASE from disk after cold-boot +## BFB001.001 Boot FreeBSD-RELEASE from disk after cold boot **Test description** This test aims to verify that FreeBSD-RELEASE could be booted from the disk -on the DUT after cold-boot. The test is performed in multiple iterations. +on the DUT after cold boot. The test is performed in multiple iterations. **Test configuration data** @@ -43,12 +43,12 @@ 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.001 Boot FreeBSD-RELEASE from disk after warm boot **Test description** This test aims to verify that FreeBSD-RELEASE could be booted from the disk -on the DUT after warm-boot. The test is performed in multiple iterations. +on the DUT after warm boot. The test is performed in multiple iterations. **Test configuration data** 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 007939e629b..4e02bbb2c16 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,12 +13,12 @@ 1. Proceed with the [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). -## BPM001.001 Boot Proxmox Virtual Environment from disk after cold-boot +## BPM001.001 Boot Proxmox Virtual Environment from disk after cold boot **Test description** This test aims to verify that Proxmox VE could be booted from the disk on -the DUT after cold-boot. The test is performed in multiple iterations. +the DUT after cold boot. The test is performed in multiple iterations. **Test configuration data** @@ -43,12 +43,12 @@ 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.001 Boot Proxmox Virtual Environment from disk after warm boot **Test description** This test aims to verify that Proxmox VE could be booted from the disk on -the DUT after warm-boot. The test is performed in multiple iterations. +the DUT after warm boot. The test is performed in multiple iterations. **Test configuration data** 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 7c382005c66..8dda292e229 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,12 +13,12 @@ 1. Proceed with the [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). -## BUS001.001 Boot Ubuntu Server LTS from disk after cold-boot +## BUS001.001 Boot Ubuntu Server LTS from disk after cold boot **Test description** This test aims to verify that Ubuntu Server LTS could be booted from the disk -on the DUT after cold-boot. The test is performed in multiple iterations. +on the DUT after cold boot. The test is performed in multiple iterations. **Test configuration data** @@ -43,12 +43,12 @@ 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.001 Boot Ubuntu Server LTS from disk after warm boot **Test description** This test aims to verify that Ubuntu Server LTS could be booted from the disk -on the DUT after warm-boot. The test is performed in multiple iterations. +on the DUT after warm boot. The test is performed in multiple iterations. **Test configuration data** 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 2bbd0ed6114..402fbb33819 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 @@ -13,12 +13,12 @@ 1. Proceed with the [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). -## BOS001.001 Boot OPNsense (serial output) from disk after cold-boot +## BOS001.001 Boot OPNsense (serial output) from disk after cold boot **Test description** 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. +disk on the DUT after cold boot. The test is performed in multiple iterations. **Test configuration data** @@ -43,12 +43,12 @@ 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.001 Boot OPNsense (serial output) from disk after warm boot **Test description** 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. +disk on the DUT after warm boot. The test is performed in multiple iterations. **Test configuration data** 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 b49ab2d3694..b1dba413f12 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 @@ -13,12 +13,12 @@ 1. Proceed with the [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). -## BOV001.001 Boot OPNsense (VGA output) from disk after cold-boot +## BOV001.001 Boot OPNsense (VGA output) from disk after cold boot **Test description** 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. +disk on the DUT after cold boot. The test is performed in multiple iterations. **Test configuration data** @@ -43,12 +43,12 @@ 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.001 Boot OPNsense (VGA output) stable from disk after warm boot **Test description** 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 +from the disk on the DUT after warm boot. The test is performed in multiple iterations. **Test configuration data** 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 5eaef5a4195..412ca62ec0f 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,12 +13,12 @@ 1. Proceed with the [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). -## BPS001.001 Boot pfSense LTS CE (serial output) from disk after cold-boot +## BPS001.001 Boot pfSense LTS CE (serial output) from disk after cold boot **Test description** This test aims to verify that pfSense LTS CE (serial output) could be booted -from the disk on the DUT after cold-boot. The test is performed in multiple +from the disk on the DUT after cold boot. The test is performed in multiple iterations. **Test configuration data** @@ -44,12 +44,12 @@ iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BPS002.001 Boot pfSense LTS CE (serial output) from disk after warm-boot +## BPS002.001 Boot pfSense LTS CE (serial output) from disk after warm boot **Test description** This test aims to verify that pfSense LTS CE (serial output) could be booted -from the disk on the DUT after warm-boot. The test is performed in multiple +from the disk on the DUT after warm boot. The test is performed in multiple iterations. **Test configuration data** 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 a1e37f7aa92..352bd6fbff3 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,12 +13,12 @@ 1. Proceed with the [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). -## BPV001.001 Boot pfSense LTS CE (VGA output) from disk after cold-boot +## BPV001.001 Boot pfSense LTS CE (VGA output) from disk after cold boot **Test description** This test aims to verify that pfSense LTS CE (VGA output) could be booted -from the disk on the DUT after cold-boot. The test is performed in multiple +from the disk on the DUT after cold boot. The test is performed in multiple iterations. **Test configuration data** @@ -44,12 +44,12 @@ iterations. The `OPERATING_SYSTEM` login screen should be displayed. -## BPV002.001 Boot pfSense LTS CE (VGA output) from disk after warm-boot +## BPV002.001 Boot pfSense LTS CE (VGA output) from disk after warm boot **Test description** This test aims to verify that pfSense LTS CE (VGA output) could be booted -from the disk on the DUT after warm-boot. The test is performed in multiple +from the disk on the DUT after warm boot. The test is performed in multiple iterations. **Test configuration data** 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 489fe0d277c..d72aeeddd59 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,12 +13,12 @@ 1. Proceed with the [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk). -## BWI001.001 Boot Windows 11 from disk after cold-boot +## BWI001.001 Boot Windows 11 from disk after cold boot **Test description** This test aims to verify that Windows 11 could be booted from the disk -on the DUT after cold-boot. The test is performed in multiple iterations. +on the DUT after cold boot. The test is performed in multiple iterations. **Test configuration data** @@ -43,12 +43,12 @@ 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 11 from disk after warm-boot +## BWI002.001 Boot Windows 11 from disk after warm boot **Test description** This test aims to verify that Windows 11 could be booted from the disk -on the DUT after warm-boot. The test is performed in multiple iterations. +on the DUT after warm boot. The test is performed in multiple iterations. **Test configuration data** diff --git a/docs/variants/novacustom_ns5x_adl/releases.md b/docs/variants/novacustom_ns5x_adl/releases.md index 218d3c1ed3e..d229db19ee5 100644 --- a/docs/variants/novacustom_ns5x_adl/releases.md +++ b/docs/variants/novacustom_ns5x_adl/releases.md @@ -51,9 +51,9 @@ Test results for this release can be found - [Connecting and immediately disconnecting the charger, sets the battery status in OS to charging for about 2 minutes (Dasharo issue #350)](https://github.com/Dasharo/dasharo-issues/issues/350) - [Reset to defaults with F9 causes the wrong settings to be restored (Dasharo issue #355)](https://github.com/Dasharo/dasharo-issues/issues/355) - [Laptop not suspending while connected to a USB-C docking station (Dasharo issue #368)](https://github.com/Dasharo/dasharo-issues/issues/368) -- [Keyboard backlight brightness is not properly restored after cold-boot (Dasharo issue #402)](https://github.com/Dasharo/dasharo-issues/issues/402) +- [Keyboard backlight brightness is not properly restored after cold boot (Dasharo issue #402)](https://github.com/Dasharo/dasharo-issues/issues/402) - [After changing the Intel ME mode the Reset option in the setup menu turns off the device (Dasharo issue #403)](https://github.com/Dasharo/dasharo-issues/issues/403) -- [The docking station is not detected after cold-boot and warm-boot (Dasharo issue #404)](https://github.com/Dasharo/dasharo-issues/issues/404) +- [The docking station is not detected after cold boot and warm boot (Dasharo issue #404)](https://github.com/Dasharo/dasharo-issues/issues/404) ### Binaries diff --git a/docs/variants/novacustom_nv4x_adl/releases.md b/docs/variants/novacustom_nv4x_adl/releases.md index db1ea0ccbca..dbb16600dc5 100644 --- a/docs/variants/novacustom_nv4x_adl/releases.md +++ b/docs/variants/novacustom_nv4x_adl/releases.md @@ -56,7 +56,7 @@ Test results for this platform can be found - [Reset to defaults with F9 causes the wrong settings to be restored (#355)](https://github.com/Dasharo/dasharo-issues/issues/355) - [Unwanted reset of BIOS settings (#365)](https://github.com/Dasharo/dasharo-issues/issues/365) - [Laptop not suspending while connected to a USB-C docking station (#368)](https://github.com/Dasharo/dasharo-issues/issues/368) -- [The docking station is not detected after cold-boot and warm-boot (#404)](https://github.com/Dasharo/dasharo-issues/issues/404) +- [The docking station is not detected after cold boot and warm boot (#404)](https://github.com/Dasharo/dasharo-issues/issues/404) ### Binaries