No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
== Step 1:Setup | == Step 1:Setup Test Environment and Check System Sanity== | ||
* 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 | == Step 2: Get Media and Check Media Sanity== | ||
* Tree compose: http://download.fedoraproject.org/pub/fedora/linux/development/[$VERSION]/[$ARCH]/os/ | * Get Media | ||
* DVD, Live, boot.iso, netinst.iso: http://dl.fedoraproject.org/pub/alt/stage/ | ** Tree compose: http://download.fedoraproject.org/pub/fedora/linux/development/[$VERSION]/[$ARCH]/os/ | ||
** Download by mirror | ** DVD, Live, boot.iso, netinst.iso: http://dl.fedoraproject.org/pub/alt/stage/ | ||
** Download by proxy (squid) | *** Download by mirror | ||
*** Download by proxy (squid) | |||
* Check Media Sanity | * Check Media Sanity | ||
Line 35: | Line 36: | ||
** file conflict for DVD | ** file conflict for DVD | ||
== Step 3: Identify | == Step 3: Identify Boot Methods, Install Repository, Partitioning, User Interface and Boot Loader== | ||
The | The test is divided into five Boot Methods as the media types: URL, DVD, Live, boot.iso and netinst.iso. | ||
All the boot methods should be able to accept different ks file, Install Repository, Partitioning, | |||
User Interface and Boot Loader. | |||
* 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 |
Revision as of 07:29, 18 November 2011
Step 1:Setup Test Environment and Check System Sanity
- 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
- Linux Desktop Test Project (LDTP)
- Logging
- service rsyslog started on host
- rsyslog listening on specific port on host
Step 2: Get Media and Check Media Sanity
- Get Media
- 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/
- Download by mirror
- Download by proxy (squid)
- Check Media Sanity
- size
- sha256sum
- md5sum
- repoclosure for DVD
- file conflict for DVD
Step 3: Identify Boot Methods, Install Repository, Partitioning, User Interface and Boot Loader
The test is divided into five Boot Methods as the media types: URL, DVD, Live, boot.iso and netinst.iso. All the boot methods should be able to accept different ks file, Install Repository, Partitioning, User Interface and Boot Loader.
- 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
Step 4: Creating Virt Guest
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 |
---|---|
URL | url_create() |
DVD,CD,boot.iso | iso_create() |
Identify potential test drivers that trigger off of those events.
- URL install source available (typically, http://download.fedoraproject.org/pub/fedora/linux/development/15/i386/os)
- url_sanity.py (for provided
images/boot.iso
) - url_install.py
- bootiso_install.py
- pxe_install.py (kind of silly, but a possible future test)
- url_sanity.py (for provided
- DVD image(s) available (typically, somewhere on http://serverbeach1.fedoraproject.org/pub/alt/stage/)
- dvd_sanity.py
- dvd_install.py
- hddvc_install.py
- nfsdvc_install.py
- CD image(s) available (typically, somewhere on http://serverbeach1.fedoraproject.org/pub/alt/stage/)
- cd_sanity.py
- cd_install.py
- hdcd_install.py
- nfscd_install.py
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 |