From Fedora Project Wiki

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 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 /url_install/ks.cfg
DVD dvd_install/ks.cfg
CD cd_install/ks.cfg
boot.iso bootiso_install/ks.cfg
Upgrade
Rescure

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