From Fedora Project Wiki
Fedora Installation Automatic Test
- 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 (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 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 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.)