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://...") |
m (Sumantrom moved page QA:Testcase partial kickstarts to QA:Testcase kickstart partial) |
||
(2 intermediate revisions by the same user not shown) | |||
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= | ||
# Install any Fedora to be tested on a bare metal system or a virtual machine. | |||
# 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= | ||
# Boot the system and interrupt the boot process to access the boot menu. | |||
# 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 | |||
# Continue with the boot process to start the Fedora installation. | |||
# Monitor the installation process to ensure that the configurations specified in the partial kickstart file are being applied. | |||
# Once the installation is complete, reboot the system. | |||
|results= | |results= | ||
# The system should boot into the installer and the installation process should initiate without any error. | |||
# The configurations specified in the partial kickstart file should be applied correctly during the installation. | |||
# The installation should complete successfully without any errors or warnings. | |||
# The system should reboot and reach the login prompt, reflecting the configurations applied from the partial kickstart file. | |||
|optional= | |optional= | ||
# Experiment with different partial kickstart files with varying configurations to check the robustness of the kickstart process. | |||
# Check the logs in /var/log/anaconda/ for any errors or warnings related to kickstart processing. | |||
}} | }} | ||
[[Category:Kickstart_test_cases]] |
Latest revision as of 16:45, 4 October 2023
Description
This test case verifies that partial kickstart files are processed correctly without any failure in the specified Fedora release.
Setup
- Install any Fedora to be tested on a bare metal system or a virtual machine.
- 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
- Boot the system and interrupt the boot process to access the boot menu.
- 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
- Continue with the boot process to start the Fedora installation.
- Monitor the installation process to ensure that the configurations specified in the partial kickstart file are being applied.
- Once the installation is complete, reboot the system.
Expected Results
- The system should boot into the installer and the installation process should initiate without any error.
- The configurations specified in the partial kickstart file should be applied correctly during the installation.
- The installation should complete successfully without any errors or warnings.
- The system should reboot and reach the login prompt, reflecting the configurations applied from the partial kickstart file.
Optional
- Experiment with different partial kickstart files with varying configurations to check the robustness of the kickstart process.
- Check the logs in /var/log/anaconda/ for any errors or warnings related to kickstart processing.