mirror of
https://github.com/Dasharo/docs.git
synced 2026-06-13 10:16:57 -07:00
docs: Visualize changes made to test ids
Signed-off-by: Filip Gołaś <filip.golas@3mdeb.com>
This commit is contained in:
Filip Gołaś
@@ -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**
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Dasharo compatibility: Custom Boot Keys
|
||||
|
||||
## CBK001.001 Custom Boot Menu Key
|
||||
## CBK001.001 Custom boot menu key
|
||||
|
||||
**Test description**
|
||||
|
||||
|
||||
+6
-10
@@ -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
|
||||
|
||||
@@ -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**
|
||||
|
||||
|
||||
+4
-4
@@ -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**
|
||||
|
||||
|
||||
@@ -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**
|
||||
|
||||
|
||||
@@ -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**
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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**
|
||||
|
||||
|
||||
@@ -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**
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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 <!-- OSFV_DOCS_SKIP -->
|
||||
|
||||
**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 <!-- OSFV_DOCS_SKIP -->
|
||||
|
||||
**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**
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -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**
|
||||
|
||||
|
||||
@@ -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**
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Dasharo Compatibility: eMMC support
|
||||
|
||||
## MMC001.001 eMMC support (Ubuntu)
|
||||
## MMC001.201 eMMC support (Ubuntu)
|
||||
|
||||
**Test description**
|
||||
|
||||
|
||||
+7
-7
@@ -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**
|
||||
|
||||
|
||||
@@ -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**
|
||||
|
||||
|
||||
+1
-1
@@ -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**
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user