From Fedora Project Wiki

Line 106: Line 106:
| ignoredisk --drives=[disk1,disk2,...]
| ignoredisk --drives=[disk1,disk2,...]
|
|
| rowspan="2"|no
| rowspan="2"|
| rowspan="2"|
| rowspan="2"|
| rowspan="2"|no
| rowspan="2"|
| rowspan="2"|
| rowspan="2"|
|-
|-
Line 125: Line 125:
| --autoscreenshot
| --autoscreenshot
|
|
|no
|
|
|
|no
|
|
|
|-
|-
Line 133: Line 133:
| --append
| --append
|
|
|rowspan="7"|yes
|rowspan="7"|
|rowspan="7"|
|rowspan="7"|
|rowspan="7"|yes
|rowspan="7"|
|rowspan="7"|
|rowspan="7"|
|-
|-
Line 183: Line 183:
| --enabled or --enable
| --enabled or --enable
|
|
|rowspan="6"|no
|rowspan="6"|
|rowspan="6"|
|rowspan="6"|
|rowspan="6"|no
|rowspan="6"|
|rowspan="6"|  
|rowspan="6"|  
|-
|-
Line 206: Line 206:
|  --enable or --enabled
|  --enable or --enabled
|
|
|rowspan="3"|no
|rowspan="3"|
|rowspan="3"|
|rowspan="3"|
|rowspan="3"|no
|rowspan="3"|
|rowspan="3"|
|rowspan="3"|
|-
|-
Line 228: Line 228:
| text
| text
|
|
| rowspan="2" |
| rowspan="2" |yes
| rowspan="2" |
| rowspan="2" |text or graphical
| rowspan="2" |
| rowspan="2" |yes
| rowspan="2" |
| rowspan="2" |text or graphical
|-
|-
| graphical
| graphical
Line 239: Line 239:
|halt
|halt
|
|
|
|no
|
|halt
|
|no
|
|halt
|-
|-
| rowspan="4"|install
| rowspan="4"|install

Revision as of 08:45, 15 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
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. The kick start options are below [1]:


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

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