From Fedora Project Wiki

Line 65: Line 65:
| rowspan=46 | Required
| rowspan=46 | Required
|-
|-
| mode
| rowspan=2| mode
| text
| text
|
|

Revision as of 09:49, 16 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 /autoinstall/url_install/url_sanity.py
DVD DVD.iso size,sha256sum, md5sum /autoinstall/dvd_install/dvd_sanity.py
CD 4 CD.iso size,sha256sum, md5sum /autoinstall/cd_install/cd_sanity.py
Minimal Boot Media boot.iso size,sha256sum, md5sum /autoinstall/bootiso_install/bootiso_sanity.py
Live live.iso size,sha256sum, md5sum /autoinstall/live_install/live_sanity.py

Step 2: Prepare kick start file to cover test cases

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 /autoinstall/url_install/url_ks.cfg
DVD /autoinstall/dvd_install/dvd_ks.cfg
CD /autoinstall/cd_install/cd_ks.cfg
boot.iso /autoinstall/bootiso_install/bootiso_ks.cfg
Upgrade

The kick start options are below [1]:


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