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 to cover test cases

Most of the test cases can be covered by configure different kick start files. Below is a basic kick start template, more options in the kick start options table can be inserted into it.

#Basic kickstart file for RATS
install
url --url=REAL_URL_GOES_HERE
lang en_US.UTF-8
keyboard us
network --device eth0 --mtu=1500 --bootproto dhcp
# "autoqa"
rootpw  --iscrypted $1$Cuh1FaJT$ogG37tqIhVDeq27uvfAYK1
timezone --utc America/New_York
# partitioning - nuke and start fresh
zerombr
clearpart --all --initlabel
autopart
bootloader --location=mbr
reboot

# packages should be a superset of critpath
%packages
@base
@base-x
%end

The kick start options are below [1]:


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

Step 3: Install Fedora with virt-install

Method to add kickstart

  • Tree Compose
  • ISO

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

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