Test Day:2009-03-05

What to test?
Today's instalment of Fedora Test Day will focus on:


 * Features/AnacondaStorageRewrite

Who's available
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
 * Development - Dave Lehman, Chris Lumens, Joel Granados
 * Quality Assurance - Robert Williams, James Laska, Adam Williamson, Will Woods

Prerequisite for Test Day

 * Rawhide fully updated (some tips below) with anaconda-11.5.0.24-3. Remember, Rawhide is an unsupported development branch: use an installation you don't mind getting broken.
 * FAS Account - you can create an account in 3 minutes if you don't have one
 * Selinux enabled. If you need to run in permissive mode please file a bug against selinux
 * (optional) - A link to your smolt profile page on Smolt

How to test
This testing effort will focus on improvements in the way in which anaconda interacts with block devices.

During this test we will focus on validation of code updates to anaconda using known good test cases. Any failures seen during this test day are especially important as they may indicate a regression in functionality from previous test results.

Test Areas
The following areas will be exercised during the execution of the defined test cases:


 * RAID
 * DMRAID
 * LVM
 * Encrypted Block Device

In addition to the baseline test cases in the table below, exploratory testing of anaconda and block devices is especially desirable.

Updates
All testing will start with rawhide. All changes for the day will be done using anaconda updates.img process. To test the latest storage fixes, you must boot with:


 * For all architectures - updates=http://dlehman.fedorapeople.org/storage/testing/updates.img

Filing Bugs
Please file bugs against Anaconda. If manually filing a bug, please set the following attributes:
 * component - anaconda
 * version - rawhide
 * whiteboard - StorageRewrite

Or just click here to start a bug report.

Test Areas and Results
In order to improve on our ability to record test results and encourage exploratory testing with the community, we are trying a different format for this test day. Instead for specific test cases, which hit different scenarios we define, a few high level 'test areas' which exercise the desired functions.

For example, we now have 3 test areas which block device types are defined as ....


 * 1) - Native (think workstation or integrated hard disks)
 * 2) - iSCSI
 * 3) - RAID (both hardware and software)

The reason for these as the major test areas is that other things like autopart, encrypted fs and ext4 could be considered functions which are applied to those test areas and anaconda interacts with them in a direct manner (that is, with fewer layers or abstractions between).