From Fedora Project Wiki

Line 61: Line 61:
|}
|}


Installation Kick Start Options
'''Installation Kick Start Options'''
{|
{|
!&nbsp !!Description !!Scripts!! Test Case
!!!Description !!Scripts!! Test Case
|-
|-
|rowspan=4 |Disk Operation
|rowspan=4 |Disk Operation
Line 100: Line 100:
</pre>
</pre>
|
|
|}
'''Upgrade Kick Start Options'''
{|
! !!Description !!Scripts!! Test Case
|-
|-
|
|rowspan=3 | Boot loader
|
|
|-
|rowspan=2 | Bootloader
|Install new bootloader
|Install new bootloader
|<pre>
|<pre>
Line 111: Line 112:
bootloader --location=mbr
bootloader --location=mbr
</pre>
</pre>
|default
|[[QA:Testcase Anaconda Upgrade New Bootloader]]
|-
|-
|Do not install a bootloader
|Do not install a bootloader
Line 118: Line 119:
bootloader --location=none
bootloader --location=none
</pre>
</pre>
|
|[[QA:Testcase Anaconda Upgrade Skip Bootloader]]
|-
|Upgrade Exiting boot loader
|<pre>
# System bootloader configuration
bootloader --location=none --upgrade
</pre>
|[[QA:Testcase Anaconda Upgrade Update Bootloader]]
|-
|}
|}



Revision as of 09:19, 17 March 2011

QA.png


This page provides a high-level roadmap for implementing the Is_anaconda_broken_proposal project. More detailed tasks can be found in autoqa TRAC roadmap. We follow these steps to define the methods by which we initiate testing

Step 1: Identify boot methods, retrieve files and check file sanity

Method Files Sanity Implementation
URL initrd.img, vmlinuz sha256sum,md5sum,version url_install/url_sanity.py
DVD DVD.iso size,sha256sum, md5sum dvd_install/dvd_sanity.py
CD 4 CD.iso size,sha256sum, md5sum cd_install/cd_sanity.py
Minimal Boot Media boot.iso size,sha256sum, md5sum bootiso_install/bootiso_sanity.py
Live live.iso size,sha256sum, md5sum live_install/live_sanity.py

Step 2: Prepare kick start file

Most of the test cases can be covered by configure different kick start files. There are kickstart templates in different installation method folders.

Method Kick Start File Template
Install URL /url_install/ks.cfg
DVD dvd_install/ks.cfg
CD cd_install/ks.cfg
boot.iso bootiso_install/ks.cfg
Upgrade
Rescure

Installation Kick Start Options

Description Scripts Test Case
Disk Operation autopart
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel 
# Disk partitioning information
autopart
QA:Testcase Anaconda autopart install
autopart encrypted
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel 
# Disk partitioning information
autopart  --encrypted --passphrase=redhat
QA:Testcase Anaconda autopart (encrypted) install
specify partition
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel 
# Disk partitioning information
part / --fstype="ext4" --size=3000
part /boot --fstype="ext4" --size=500
part swap --fstype="swap" --size=500

Upgrade Kick Start Options

Description Scripts Test Case
Boot loader Install new bootloader
# System bootloader configuration
bootloader --location=mbr
QA:Testcase Anaconda Upgrade New Bootloader
Do not install a bootloader
# System bootloader configuration
bootloader --location=none
QA:Testcase Anaconda Upgrade Skip Bootloader
Upgrade Exiting boot loader
# System bootloader configuration
bootloader --location=none --upgrade
QA:Testcase Anaconda Upgrade Update Bootloader

List test scenarios,it will make clear that which suite needs to support.

Step 3: Install Fedora

from virtguest import VirtGuest, the methods to initialize a guest for both tree compose and iso image have been implemented.

Identify potential test drivers that trigger off of those events.

Step 5

Write test drivers using requirements gathered in steps #2,#3,#4


Key

Set priorities for each test. The test drivers will support the tests with high priority.

Colour Explanation
yes supported and default (high priority)
yes supported (medium priority)
yes supported (low priority)
no unsupported configuration
unknown unknown

References