From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 29: | Line 29: | ||
##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 ( | ##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 not block the installation, exception occurs and blocks 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 | ||
| Line 36: | Line 36: | ||
##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 and explore the Python libraries of AutoQA, such as util etc, but it seems there is no documentation. | ||
##explore the | ##explore the files of Fedora, such as .treeinfo, initrd etc. which I need to deal during development. | ||
#Questions | #Questions | ||
##where to find the AutoQA arguments? | ##where to find the AutoQA arguments? | ||
Revision as of 07:32, 31 December 2010
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.
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!
- Platform
- virt-manager/lib-virt+KVM
- Development
- 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
- detect the prerequirements (arch etc) of the Fedora installation and create the suitable KVM machines.
- start to install fedora (which installation mode to choose)
- log the test result. (cases: installation successes, exception occurs but not block the installation, exception occurs and blocks 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 and explore the Python libraries of AutoQA, such as util etc, but it seems there is no documentation.
- explore the files of Fedora, such as .treeinfo, initrd etc. which I need to deal during development.
- Questions
- where to find the AutoQA arguments?