From Fedora Project Wiki

No edit summary
No edit summary
 
(37 intermediate revisions by the same user not shown)
Line 1: Line 1:
<h1>Fedora Installation Automatic Test</h1>
__NOTOC__
{{Template:Userpage/Infobox2
|REAL-NAME=Hongqing, YANG
|HOME=https://fedoraproject.org/wiki/User:Hongqing
|FAS-NAME=hongqing
|IRC=hongqing
|irc-channels=#fedora-qa, #fedora-test-day, #fedora-meeting
|image=hongqing_fp.jpg
}}
==About==
Thanks for visiting my page! I am a Fedora Quality Assurance Engineer and now I am working on the project Fedora installation test automation.<br/>
I start to use Fedora when I was a student and developed the molecular simulation project on Linux platform.
 
==Auto Test==
*auto test: http://autotest.kernel.org
*autoQA: http://fedoraproject.org/wiki/AutoQA
*writing autoQA test: http://fedoraproject.org/wiki/Writing_AutoQA_Tests
*verifying autoQA test:http://fedoraproject.org/wiki/Verifying_AutoQA_tests
 
==Languages==
*Python
**Style Guide for Python Code:http://www.python.org/dev/peps/pep-0008/
==Virtualization==
*get started with virtualization:http://fedoraproject.org/wiki/Virtualization_Quick_Start
*libvirt: http://libvirt.org/index.html
*virt-manager:http://virt-manager.et.redhat.com/
*KVM:http://www.linux-kvm.org/page/Main_Page
==Fedora Installation Test Automation==
{{admon/note|Note:|This is for personal note, please do not refer this.}}
{{admon/note|Note:|This is for personal note, please do not refer this.}}
* Fedora Desktop
**GNOME,KDE,LXDE,Xfce
* Fedora Installation methods:
* Fedora Installation methods:
**CD/DVD
**CD/DVD
**Hard Drive
**Hard Drive
**NFS/URL
**HTTP Server, FTP Server, NFS Server
**ISO images on NFS Server.
**Live USB
**Live USB
* Fedora Support Platform
* Fedora Support Platform
Line 21: Line 51:
##trigger Testing, refer the current test events being monitored: http://git.fedorahosted.org/git/?p=autoqa.git;a=tree;f=hooks
##trigger Testing, refer the current test events being monitored: http://git.fedorahosted.org/git/?p=autoqa.git;a=tree;f=hooks
##Check installation media, refer QA:Installer image presence test case http://fedoraproject.org/wiki/QA:Installer_image_presence_test_case
##Check installation media, refer QA:Installer image presence test case http://fedoraproject.org/wiki/QA:Installer_image_presence_test_case
##detect the prerequirements (arc etc) of the Fedora installation and create the suitable KVM machines.
##detect the prerequirements (arch etc) of the Fedora installation and create the suitable KVM machines.
##start to install fedora (which mode to choose)
##start to install fedora (which installation mode to choose)
##log the test result. (cases: installation successes, exception occurs but do not block the installation, exception occurs and block the installation).  
##log the test result. (cases: installation successes, exception occurs but not block the installation, exception occurs and blocks the installation).  
 
#Works need to do
*Works need to do
##explore trigger (AutoQA current monitored events)
**explore trigger (AutoQA current monitored events)
##check installation media (This has been done in AutoQA, still need to explore how to call it.)
**check installation media (This has been done in AutoQA, still need to explore how to call it.)
##access the AutoTest Server from AutoQA client and explore the Python libraries of AutoQA, such as util etc, but it seems there is no documentation.
**access the AutoTest Server from AutoQA client.
##explore the files of Fedora, such as .treeinfo, initrd etc. which I need to deal during development.
**explore the contents of different files of Fedora, such as .treeinfo, initrd etc. which I need to deal during development.
#Questions
**read the parameters from hook files during the installation in different mode (anaconda, kernel, etc.)
##where to find the AutoQA arguments?
== References ==
<references/>

Latest revision as of 06:46, 26 April 2012

Hongqing, YANG
Hongqing, YANG
Hongqing, YANG
Fedora Information
FAS name: hongqing
Fedora email: hongqing@fedoraproject.org
IRC nick: hongqing
IRC channels: #fedora-qa, #fedora-test-day, #fedora-meeting
Fedorapeople page: https://hongqing.fedorapeople.org
Badges (0)
 

About

Thanks for visiting my page! I am a Fedora Quality Assurance Engineer and now I am working on the project Fedora installation test automation.
I start to use Fedora when I was a student and developed the molecular simulation project on Linux platform.

Auto Test

Languages

Virtualization

Fedora Installation Test Automation

Note:
This is for personal note, please do not refer this.
  • Fedora Desktop
    • GNOME,KDE,LXDE,Xfce
  • Fedora Installation methods:
    • CD/DVD
    • Hard Drive
    • HTTP Server, FTP Server, NFS Server
    • ISO images on NFS Server.
    • Live USB
  • Fedora Support Platform
    • x86
    • x86_64
    • IA64
    • ARM
  • Fedora Support CPUs
    • Macintosh
    • Intel, AMD
    • ...

It seems huge, if we wanna cover all!

  1. Platform
    1. virt-manager/lib-virt+KVM
  2. Development
    1. trigger Testing, refer the current test events being monitored: http://git.fedorahosted.org/git/?p=autoqa.git;a=tree;f=hooks
    2. Check installation media, refer QA:Installer image presence test case http://fedoraproject.org/wiki/QA:Installer_image_presence_test_case
    3. detect the prerequirements (arch etc) of the Fedora installation and create the suitable KVM machines.
    4. start to install fedora (which installation mode to choose)
    5. log the test result. (cases: installation successes, exception occurs but not block the installation, exception occurs and blocks the installation).
  3. Works need to do
    1. explore trigger (AutoQA current monitored events)
    2. check installation media (This has been done in AutoQA, still need to explore how to call it.)
    3. access the AutoTest Server from AutoQA client and explore the Python libraries of AutoQA, such as util etc, but it seems there is no documentation.
    4. explore the files of Fedora, such as .treeinfo, initrd etc. which I need to deal during development.
  4. Questions
    1. where to find the AutoQA arguments?

References