From Fedora Project Wiki

No edit summary
No edit summary
Line 20: Line 20:
#Development
#Development
##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
##detect the prerequirements of the Fedora installation.
##create the suitable KVM machines.
##start to install fedora, and also need
##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
##Install fedora on different archs
##detect the prerequirements (arc etc) of the Fedora installation and create the suitable KVM machines.
##Installation successes, exception occurs but do not block the installation, exception occurs and block the installation.  
##start to install fedora (which mode to choose)
#Development
##log the test result. (cases: installation successes, exception occurs but do not block the installation, exception occurs and block the installation).  
##AutoQA patch Process, refer: http://fedoraproject.org/wiki/AutoQA_Patch_Process
##How to download installation media from Koji and Bodhi refer: The current test events being monitored. http://git.fedorahosted.org/git/?p=autoqa.git;a=tree;f=hooks or Writing AutoQA Hooks http://fedoraproject.org/wiki/Writing_AutoQA_Hooks or by command virt-install.
##How to check the images and archs
##How to call virt-manager by command from Python
##How to create different virtual machines from command.
##How to log the test result.
*Example of bash script to install Fedora on KVM
  <pre>
#!/bin/bash
virt-install \
--connect qemu:///system \
--virt-type kvm \
--name demo \
--ram 500 \
--disk path=~/Desktop/fedora/Fedora-14-i686-Live-Desktop.iso,size=8 \
--vnc \
--cdrom /dev/cdrom \
--os-variant fedora14


  </pre>
*Works need to do
 
**explore trigger (AutoQA current monitored events)
 
**check installation media (This has been done in AutoQA, still need to explore how to call it.)
 
**access the AutoTest Server from AutoQA client.
*How to write AutoQA  http://fedoraproject.org/wiki/Writing_AutoQA_Tests
**explore the contents of different files of Fedora, such as .treeinfo, initrd etc. which I need to deal during development.
*How to login AutoTest Server?
**read the parameters from hook files during the installation in different mode (anaconda, kernel, etc.)
*Python works with bash o.system("command")
*git, is git a version control tool?
*How to capture the Fedora UI during the installation
*What is on the autotest server? KVM? virt-manager?

Revision as of 05:33, 30 December 2010

Fedora Installation Automatic Test

Note:
This is for personal note, please do not refer this.
  • Fedora Installation methods:
    • CD/DVD
    • Hard Drive
    • NFS/URL
    • 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 (arc etc) of the Fedora installation and create the suitable KVM machines.
    4. start to install fedora (which mode to choose)
    5. log the test result. (cases: installation successes, exception occurs but do not block the installation, exception occurs and block the installation).
  • Works need to do
    • explore trigger (AutoQA current monitored events)
    • check installation media (This has been done in AutoQA, still need to explore how to call it.)
    • access the AutoTest Server from AutoQA client.
    • explore the contents of different files of Fedora, such as .treeinfo, initrd etc. which I need to deal during development.
    • read the parameters from hook files during the installation in different mode (anaconda, kernel, etc.)