From Fedora Project Wiki

Revision as of 06:22, 27 November 2009 by Rhe (talk | contribs) (Problem Space)


provide small auto-test system with a web-based interface which can help to customize autoinstall testing.The test system should be small enough for personal use.

Problem Space

The purpose of auto test is to simplify testing,save time, improve efficiency.So the auto-test should help us to solve the following problems:

  • the system should be small enough for personal use
  • have a very simple interface for user to customize testing or configure testing
  • very easy interface for user to set up some services due to some special cases,such as ftp/nfs/http install,etc
  • test result is easy to check

Installation process covers the following sections, therefore Brokenness comes from these types:

  • Image Sanity:
  • Boot Methods
  1. The CD/DVD isolinux (or syslinux) menu is properly displayed
  2. Anaconda boots successfully from the DVD
  3. Anaconda transitions to stage#2 without error
  • Install Source
  1. Install completes successfully
  2. Package errors (install.log) should not occur
  3. System boots successfully
  • Kickstart Delivery
  1. The ks.cfg is successfully obtained from the specified location
  2. The install should proceed in accordance with the directives in the ks.cfg file
  • Package Set
  1. Anaconda completes successfully
  2. System boots into installed environment successfully
  3. Install.log does not contain errors
  4. A (small) number of packages is installed (150~)
  • Partitioning
  1. The system should prompt for your passphrase only once during boot
  2. The system unlocks the encrypted partition(s) and boots successfully
  3. Anaconda should prompt for an existing partition to resize
  4. Anaconda should successfully resize the selected partition
  5. The installer will successfully partition a bootable system using remaining free space
  6. Confirm that rootfs partition is formatted as ext4/3/2 and is not a LVM or RAID volume
  7. Partitions are created and formatted properly.
  • User Interface
  1. Graphical anaconda displays properly
  2. The installed system boots in graphical mode (runlevel 5)
  3. Anaconda starts Xvnc/telnet properly
  • Recovery
  • Storage Devices
  • Upgrade system

Proposed Solution

  • use the network install(or libvirt? does it make sense to run on virtual machines? need confirmation) to finish install tests one by one.
  • provide web-based interface to customize testing.In the web page,user can specify the path of ISO,select which cases to run or not,edit(import) kickstart file or automaticly generate kickstart file after give some selected parameters (partition,packages,install method).
  • web-based interface help to setup some needed services due to some special cases. Modify,add or delete test cases,
  • Test result display page help to check the test result easily,the result format is good for testers to post to specified link(have no need to change a lot before post).


  • Any testers from community can install the testing system and run test cases
  • After finish testing,testers will post test result to specified wiki

Active Ingredients

  • develop a system to run install system
  • convert some of the current install test cases to cases which can be run in auto test system
  • Provide a test results presentation layer for manual test result submission


your comments


Version 1.0

  • Goal: Create a basic system, make it simple and run successfully.
  • Case: DVD input and support simplest test cases.
  • Platform: Virtual Machine.
  • Inputs and Outputs:
    • Inputs: DVD, kickstart files, python (shell) scripts.
    • Outputs: Logs of whole process(including anaconda logs), test results.
  • Approach<<Fix Me>>:
  1. Create a server, and prepare DVD.iso.
  2. Create a virtual machine by the server.
  3. Run test cases using some kickstarts for install tests.
  4. Send back some logs, successful or not...
  5. Have some "results parsers" which waits for the logs from the clients and then parses them
  • Frameworks studied so far: kvm-autotest, autotest, libvirt, dogtail.

Version 2.0

  • Graphical automation testing
  2. The above autotest is based on this framework:
  3. The steps to work with step files:

Discussion Points

your comments


To leave a comment, use the Talk page for this proposal.


Fedora auto-install test project


This project meeting is held weekly for progress. Welcome everyone to attend it and give your valuable suggestions.

  • IRC on #fedora-meeting
  • Each Friday at 8:30 UTC (9:30 CET and 16:30 Bejing)