User:Hongqing

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.
FAS name: hongqing
Email: hoyang@redhat.com
IRC channel: #fedora-qa,#fedora-meeting,#fedora-test-day

Fedora Installation Test Automation

Note:
This is for personal note, please do not refer this.

• 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 (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 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 contents of different files of Fedora, such as .treeinfo, initrd etc. which I need to deal during development.
   5. read the parameters from hook files during the installation in different mode (anaconda, kernel, etc.)
4. Questions
   1. where to find the AutoQA arguments?