From Fedora Project Wiki
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
DVD DVD.iso exits DVD size
CD 4 CDs exit, CD size
Minimal Boot Media boot.iso exits Sanity
PXE initrd.img, vmlinuz exit Sanity

Step 2: Write kick start file

Most of the test cases can be covered by configure different kick start files. The kick start options are below:

Options Values
autopart encrypted passphrase

Step 2

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

  Boot Method [1]
Test DVD CD boot.iso PXE images efidisk.img Live Image
Installation Method [2][3]  
autodetect cdrom yes yes yes yes yes no
repo=cdrom yes yes yes yes yes no
repo=http://host/path yes yes yes yes yes no
repo=ftp://[user:passwd@]server/path yes yes yes yes yes no
repo=nfs:server:/path yes yes yes yes yes no
repo=nfsiso:server:/path yes yes yes yes yes no
repo=hd:device/path yes yes yes yes yes no
repo=hdiso: yes yes yes yes yes no
repo=livecd: no no no no no yes
Methods to locate kickstart file [3]  
ks (autodetect from dhcp ???(default is nfs)) yes yes yes yes yes unknown
ks=http://server/path yes yes yes yes yes unknown
ks=ftp://[user:passwd@]server/path yes yes yes yes yes unknown
ks=nfs:server:/path yes yes yes yes yes unknown
ks=file:/path yes yes yes yes yes unknown
ks=hd:device:/path yes yes yes yes yes unknown
ks=bd:biosdevice:/path yes yes yes yes yes unknown
ks=floppy yes yes yes yes yes unknown
ks=cdrom yes yes yes yes yes unknown
Methods to locate updates.img  
updates yes yes yes yes yes no
updates=http yes yes yes yes yes no
images/updates.img no no no yes yes no
RHUpdates no no no yes yes no
Methods to determine display device  
graphical yes yes yes yes yes yes
text yes yes yes yes yes yes
vnc yes yes yes yes yes no
cmdline yes yes yes yes yes no
serial console=ttyS0 yes yes yes yes yes no
telnet yes yes yes yes yes no
Methods to choose kickstart network device [3]  
ksdevice=link yes yes yes yes yes no
ksdevice=bootif yes yes yes yes yes no
ksdevice=eth0 yes yes yes yes yes no
ksdevice=AA:BB:CC:DD:EE:FF yes yes yes yes yes no
Methods to activate network device  
ip=dhcp yes yes yes yes yes no
ip=a.b.c.d yes yes yes yes yes no
dns= yes yes yes yes yes no
gateway= yes yes yes yes yes no
netmask= yes yes yes yes yes no

step 3

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

step 4

Identify potential test drivers that trigger off of those events.

Step 5

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

Step 6

Write kickstart files to exercise the tests identified in step#2

References