No edit summary |
|||
Line 124: | Line 124: | ||
== Roadmap == | == Roadmap == | ||
* Roadmap for development of auto install at:[[Is_anaconda_broken_roadmap]] | |||
* Status for test plan/documentation changes can be seen in the [https://fedorahosted.org/fedora-qa/query?status=new&status=assigned&status=reopened&status=closed&group=status&component=Test+Review&milestone=Fedora+13&order=priority fedora-qa trac system] | * Status for test plan/documentation changes can be seen in the [https://fedorahosted.org/fedora-qa/query?status=new&status=assigned&status=reopened&status=closed&group=status&component=Test+Review&milestone=Fedora+13&order=priority fedora-qa trac system] | ||
* Status for test automation efforts is available in the [https://fedorahosted.org/autoqa/milestone/Automate%20installation%20test%20plan autoqa TRAC system] | * Status for test automation efforts is available in the [https://fedorahosted.org/autoqa/milestone/Automate%20installation%20test%20plan autoqa TRAC system] | ||
== Results == | == Results == |
Revision as of 09:05, 19 May 2010
Overview
The purpose of AutoQA install test automation is to simplify testing, reduce the test execution time and improve efficiency. The AutoQA install test project should address the following problems:
- The system should be easy to allow for tester and developer use
- Have clear documentation for customizing and creating new tests
- Support test execution using existing Fedora infrastructure services, but not require them
- Test results are easy to verify
Problem Space
The Fedora installer is a complicated software application that often requires significant setup time to properly and efficiently test. Installer failures typically come from the following areas:
Image Sanity
- ISO file size is too large (or small)
- Invalid SHA256 checksum
- Invalid implanted ISO md5sum
- Install environment - anaconda has specific application, library and config file format requirements.
- Versions check
Boot Methods
- Boot media improperly built (PXE, boot.iso, CD/DVD, efidisk.img)
- Installer fails to boot as a KVM guest
- Installer fails to boot as a XEN guest
Install Source
- Unable to detect install.img media
- Unable to transition to stage#2 installer
Kickstart Delivery
- Ks.cfg could not be obtained from specified location (http, ftp, nfs, hd, initrd)
- Install fails to proceed in accordance with the directives in the ks.cfg file
- Install improperly sets up networking based on command-line and kickstart network parameters (boot with
ksdevice=eth1
,ks.cfg
containseth2
)
User Interface
- X driver problems while transitioning to graphical install
- Screen corruption during text-mode install
- VNC fails to start
- Serial console redirection improperly setup
Storage Devices
- Fail to detect existing storage device(s)
- Failure to clear stale data off of existing devices
- Unable to add iSCSI volumes
Partitioning
- Failure detecting existing partition scheme (lvm, mdraid, dmraid, luks)
- Failure when attempting to resize existing partitions
- Failures while attempting to re-use existing partitions
- Improperly clearing stale information from disks
- Unable to consistently resize an existing filesystem
- General failures while attempting to manually partition a system
Package Repository
- Unable to read metadata from package repositories (http, ftp, nfs, media)
- Failures while adding or modifying existing package repositories
Package Set
- Network timeout while retrieving packages
- Dependency problems while resolving package list
- File conflicts during package install
- Package order and install errors in
install.log
- Improperly formatted
comps.xml
data
Boot loader configuration
- Unable to properly detect other operating systems
- Failure while setting up chainloader for another OS
Upgrade system
- Failure to detect previously installed systems
- Errors while attempting to update bootloader configuration during upgrade
- Package upgrade errors in
upgrade.log
Recovery
- Rescue mode fails to detect existing installations (lvm, raid, luks)
- Rescue mode fails to establish networking
- Problems saving traceback information (local disk, bugzilla, remote server)
- Anaconda unable to download and use updates.img (from install source, local media or URL)
- Unable to transition to debug mode
Proposed Solution
First, in order to provide a consistent and documented test approach, the existing Fedora Install test plan [1] will be revisited. The test plan will be adjusted to ensure proper test coverage for the failure scenarios listed above. Existing test cases will be reviewed for accuracy. New test cases will be created using the Template:QA/Test_Case template. Finally, the test plan will be adjusted to match the improved Fedora Release Criteria [2]. This includes adjusting the test case priority to match milestone criteria.
Next, in order to reduce the setup/execution time, improve efficiency and to provide test results on a more consistent basis, a subset of test cases will be chosen for automation. Tests will be written in python and will be developed and executed on a system supporting KVM virtualization. Test scripts will be responsible for preparing a virtual install environment, initiating a kickstart install and validating the results. Once an initial batch of tests exist, they will be formally integrated into the AutoQA project.
Last, a method will be developed for collecting test results into a single test result matrix. Results may be posted to the wiki directly, or a custom turbogears application may be needed to display results [3]. The results will be easily accessible for testers and the installer development team.
Scope
The project will be divided into several phases.
Phase#1 - proof of concept
- Revise Fedora Install test plan to ensure adequate test coverage exists for failure scenarios listed above
- Select a small, but representative, subset of test cases from the install test plan to automate
- Create python scripts to prepare KVM-based virtual environments for testing, initiate kickstart installs, and validate results
- Investigate methods for leveraging GUI automation to aid in automating applicable test cases
Phase#2 - implementation
- Identify and automate remainder of test cases from the install test plan
- Identify and integrate anaconda built-in unit tests into tests
- Identify test event triggers which will be used to automatically initiate testing.
- Identify test cases where GUI automation will be required
Phase#3 - integration
- Create appropriate control files and test wrappers to allow for scheduling tests through AutoQA (see Writing_AutoQA_Tests)
- Develop or update AutoQA test event hooks to accommodate new test events (see Writing_AutoQA_Hooks)
- Implement initial test result dashboard intended to eventually replace the wiki test matrix. The dashboard will also support FAS user test result submission. This will likely rely on
Active Ingredients
- AutoQA must be packaged and available in Fedora infrastructure
- A valid backend test harness is packaged and available in Fedora infrastructure (Autotest currently being used by AutoQA)
- Knowledge of TurboGears or TurboGears2
- A new AutoQA test watcher may be required to initiate automated tests whenever CD and DVD ISO images are available for testing (post-iso-build)
- Adding installer unit test execution and results display is dependent on the availability and environmental requirements of installer unit tests
Roadmap
- Roadmap for development of auto install at:Is_anaconda_broken_roadmap
- Status for test plan/documentation changes can be seen in the fedora-qa trac system
- Status for test automation efforts is available in the autoqa TRAC system
Results
- Meeting information and logs can be found at Is_anaconda_broken_meeting
Discussion Points
- List unresolved or active discussion
Comments?
To leave a comment, use the Talk page for this proposal.
Owner
Fedora QA team
References
- ↑ QA:Fedora_13_Install_Test_Plan
- ↑ Fedora Release Criteria
- ↑ For a similar project see screenshot of is rawhide broken and source code and the QA:Rawhide_Acceptance_Test_Plan.
Other documentation:
- General libvirt home - http://libvirt.org
- Examples on using libvirt and cobbler to aid in semi-automated install testing - http://jlaska.livejournal.com/tag/cobbler
- General Autotest information
- KVM is using autotest
- GUI automation using dogtail - https://fedorahosted.org/dogtail
- GUI automation using autotest step files - http://www.linux-kvm.org/page/KVM-Autotest/Steps