From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 16: | Line 16: | ||
**... | **... | ||
'''It seems huge, if we wanna cover all!''' | '''It seems huge, if we wanna cover all!''' | ||
*Platform | |||
##virt-manager/lib-virt+KVM | ##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 | ##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 | ||
Line 25: | Line 25: | ||
##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 do not block the installation, exception occurs and block the installation). | ||
*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.) |
Revision as of 05:36, 30 December 2010
Fedora Installation Automatic Test
- 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!
- 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 (arc etc) of the Fedora installation and create the suitable KVM machines.
- start to install fedora (which mode to choose)
- 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.)
- explore the commands of AutoQA.