From Fedora Project Wiki

(Created page with "{{QA/Test_Case |description=This test case verifies that partial kickstart files are processed correctly without any failure in the specified Fedora release. |setup= 1. Install any Fedora to be tested on a bare metal system or a virtual machine. 2. Ensure that you have a partial kickstart file prepared for the test. The partial kickstart file should include a few basic configurations like user creation, package installation, and disk partitioning. You can user https://...")
 
No edit summary
Line 2: Line 2:
|description=This test case verifies that partial kickstart files are processed correctly without any failure in the specified Fedora release.
|description=This test case verifies that partial kickstart files are processed correctly without any failure in the specified Fedora release.
|setup=
|setup=
1. Install any Fedora to be tested on a bare metal system or a virtual machine.
# Install any Fedora to be tested on a bare metal system or a virtual machine.
2. Ensure that you have a partial kickstart file prepared for the test. The partial kickstart file should include a few basic configurations like user creation, package installation, and disk partitioning. You can user [[https://fedorapeople.org/groups/qa/kickstarts/example-minimal.ks]] this
# Ensure that you have a partial kickstart file prepared for the test. The partial kickstart file should include a few basic configurations like user creation, package installation, and disk partitioning. You can use this [[https://fedorapeople.org/groups/qa/kickstarts/example-minimal.ks]]
|actions=
|actions=
1. Boot the system and interrupt the boot process to access the boot menu.
# Boot the system and interrupt the boot process to access the boot menu.
2. At the boot menu, append the ks parameter to the kernel line, pointing to the location of your partial kickstart file. For example: ks=http://path/to/your/partial.ks
# At the boot menu, append the ks parameter to the kernel line, pointing to the location of your partial kickstart file. For example: ks=http://path/to/your/partial.ks
3. Continue with the boot process to start the Fedora installation.
# Continue with the boot process to start the Fedora installation.
4. Monitor the installation process to ensure that the configurations specified in the partial kickstart file are being applied.
# Monitor the installation process to ensure that the configurations specified in the partial kickstart file are being applied.
5. Once the installation is complete, reboot the system.
# Once the installation is complete, reboot the system.
|results=
|results=
1. The system should boot into the installer and the installation process should initiate without any error.
# The system should boot into the installer and the installation process should initiate without any error.
2. The configurations specified in the partial kickstart file should be applied correctly during the installation.
# The configurations specified in the partial kickstart file should be applied correctly during the installation.
3. The installation should complete successfully without any errors or warnings.
# The installation should complete successfully without any errors or warnings.
4. The system should reboot and reach the login prompt, reflecting the configurations applied from the partial kickstart file.
# The system should reboot and reach the login prompt, reflecting the configurations applied from the partial kickstart file.
|optional=
|optional=
1. Experiment with different partial kickstart files with varying configurations to check the robustness of the kickstart process.
# Experiment with different partial kickstart files with varying configurations to check the robustness of the kickstart process.
2. Check the logs in /var/log/anaconda/ for any errors or warnings related to kickstart processing.
# Check the logs in /var/log/anaconda/ for any errors or warnings related to kickstart processing.
}}
}}

Revision as of 04:42, 4 October 2023

Description

This test case verifies that partial kickstart files are processed correctly without any failure in the specified Fedora release.

Setup

  1. Install any Fedora to be tested on a bare metal system or a virtual machine.
  2. Ensure that you have a partial kickstart file prepared for the test. The partial kickstart file should include a few basic configurations like user creation, package installation, and disk partitioning. You can use this [[1]]

How to test

  1. Boot the system and interrupt the boot process to access the boot menu.
  2. At the boot menu, append the ks parameter to the kernel line, pointing to the location of your partial kickstart file. For example: ks=http://path/to/your/partial.ks
  3. Continue with the boot process to start the Fedora installation.
  4. Monitor the installation process to ensure that the configurations specified in the partial kickstart file are being applied.
  5. Once the installation is complete, reboot the system.

Expected Results

  1. The system should boot into the installer and the installation process should initiate without any error.
  2. The configurations specified in the partial kickstart file should be applied correctly during the installation.
  3. The installation should complete successfully without any errors or warnings.
  4. The system should reboot and reach the login prompt, reflecting the configurations applied from the partial kickstart file.

Optional

  1. Experiment with different partial kickstart files with varying configurations to check the robustness of the kickstart process.
  2. Check the logs in /var/log/anaconda/ for any errors or warnings related to kickstart processing.


Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_kickstart_partial&oldid=690620"