From Fedora Project Wiki

No edit summary
No edit summary
Line 1: Line 1:
== Step 1:Setup Test Environment and Check System Sanity==
== Test Environment ==
* Virtualization
* Virtualization
** python-fedora installed
** python-fedora installed
Line 22: Line 22:
** rsyslog listening on specific port on host
** rsyslog listening on specific port on host


== Step 2: Get Media and Check Media Sanity==
== Download Images==
* Get Media
* Get Images
** Tree compose: http://download.fedoraproject.org/pub/fedora/linux/development/[$VERSION]/[$ARCH]/os/
** Tree compose: http://download.fedoraproject.org/pub/fedora/linux/development/[$VERSION]/[$ARCH]/os/
** DVD, Live, boot.iso, netinst.iso: http://dl.fedoraproject.org/pub/alt/stage/
** DVD, Live, boot.iso, netinst.iso: http://dl.fedoraproject.org/pub/alt/stage/
Line 29: Line 29:
*** Download by proxy (squid)
*** Download by proxy (squid)


* Check Media Sanity
== Image Sanity ==
** size
* size
** sha256sum
* sha256sum
** md5sum
* md5sum
** repoclosure for DVD
* repoclosure for DVD
** file conflict for DVD
* file conflict for DVD


== Step 3: Identify Boot Methods, Install Repository, Partitioning, User Interface and Boot Loader==
== Logging ==
The test is divided into five Boot Methods as the media types: URL, DVD, Live, boot.iso and netinst.iso.
* serial console
All the boot methods should be able to accept different ks file, Install Repository, Partitioning,
* Anaconda Logging
User Interface and Boot Loader.


== Create Guest ==
* virt-install
== Boot Arguments ==
* virt-install options
* Accessibility
* LDTP or dogtail
* kick start can be passed by virt-install arguments for tree compose or terminal for ISOs
* kick start can be passed by virt-install arguments for tree compose or terminal for ISOs
** remote kickstart files: http, ftp, nfs
** remote kickstart files: http, ftp, nfs
Line 60: Line 66:
The mapping of test cases with kick start files can be found at  [[Testcase_Kickstart_Mapping]]
The mapping of test cases with kick start files can be found at  [[Testcase_Kickstart_Mapping]]


== Virtue Disk ==
* libguestfs


== Step 4: Creating Virt Guest==
== Watcher ==
virt-install is adopted to initialize the guest. The functions to create guest with virt-install from url, DVD,ect. should be defined firstly.
The following functions are defined in the class '''VirtGuest''' located in '''/lib/python/virtguest.py'''.
{|
!Method!!Function
|-
|width=100|URL
|width= 200|url_create()
|-
|DVD,CD,boot.iso
|iso_create()
|}
 
 


Identify potential test drivers that trigger off of those events.
Identify potential test drivers that trigger off of those events.

Revision as of 07:41, 18 November 2011

Test Environment

  • Virtualization
    • python-fedora installed
    • libvirt installed
    • qemu-kvm installed
    • python-virtinst installed
    • pax installed
    • service libvirtd started
  • Virtual disk (required for hd installation and ks hosted on hd)
    • libguestfs installed
    • python-libguestfs installed
  • Interaction with Desktop
    • Linux Desktop Test Project (LDTP)
      • ldtp installed
      • python-ldtp installed
    • dogtail
  • Logging
    • service rsyslog started on host
    • rsyslog listening on specific port on host

Download Images

Image Sanity

  • size
  • sha256sum
  • md5sum
  • repoclosure for DVD
  • file conflict for DVD

Logging

  • serial console
  • Anaconda Logging

Create Guest

  • virt-install

Boot Arguments

  • virt-install options
  • Accessibility
  • LDTP or dogtail
  • kick start can be passed by virt-install arguments for tree compose or terminal for ISOs
    • remote kickstart files: http, ftp, nfs
    • local kickstart files: ks file should be uploaded on to the virtdisk before using it
  • repo
    • passed by terminal
    • passed by ks file
  • partitioning
    • passed by ks file
  • user interface
    • passed by terminal
  • boot loader
    • passed by ks file

The mapping of test cases with kick start files can be found at Testcase_Kickstart_Mapping

Virtue Disk

  • libguestfs

Watcher

Identify potential test drivers that trigger off of those events.

Step 5 : Logging and watching the steps of installation

Get the installation output and logs at every step:

Stage Log file End label
Boot boot.log Greetings
Stage1 stage1.log Running anaconda [version], system installer - please wait
Stage2 stage2.log

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