User:Johannbg/Draft/QA/Test Days/Features/EXT4

DATE	TIME	WHERE
$Date	From $Time to $Time UTC	#fedora-qa (need irc help?)

How to join?

For information on joining a Fedora Test Day, see QA/Test_Days#Where_are_Test_Days_held.3F

What to test?

This week's instalment of Fedora Test Day will focus on:

• Features/20SecondStartup

Preparing for Test Day

Depending on the speed of your connection and the time available for testing, there are several methods available for

Live Images

1. Please download a live ISO image for your architecture:
   • i686
   • x86_64
2. Prepare your live image by following the instructions at FedoraLiveCD
3. Or run the dowloaded ISO image in qemu:

    su -c 'qemu -cdrom Fedora-11-Alpha-i686-Live.iso -m 512 -std-vga'

Install Media

1. Consult the installation guide for quick start information to determine the best install method for your needs.
2. Follow instructions for installing your system.
   • Alternatively, on an already installed system:
     1. Install snake:

        yum install snake

     2. Configure your system for installation:

        snake-install http://download.fedora.redhat.com/pub/fedora/linux/releases/test/11-Alpha/Fedora/i386/os

Test Plan

Test Case: Assign ext4 fs with mount point How to test:

  1. Prepare system with ext4 filesystem(s).
  2. Boot the installer.
  3. Select the ext4 filesystem as a mount point except of /boot, preferably some 'data' filesystem.
  4. Ensure installation is finished successfully.

Expected Results:

   * ext4 filesystems are recognized.
   * Mount point can be assigned to ext4 filesystem.
   * Installation completes successfully.
   * System starts properly with all filesystems mounted.

---

Test Case: Identify ext4 filesystems How to Test:

  1. Prepare system with ext4 filesystem(s).
  2. Boot the installer.
  3. Use "Create custom layout" for partitioning and keep existing partitions.
  4. Ensure ext4 filesystems are recognized and included in list of filesystems.

Expected Results:

   * Anaconda starts successfully.
   * ext4 filesystems are detected and listed in partition layout of Disk druid screen.
   * Disk druid allows basic manipulation with ext4 filesystems.

---

Test Case: Create new ext4 partition (non-root fs) How to Test:

   1. Boot the installer
   2. Advance to the (ddruid) partitioning screen
   3. Create a new (or use existing) partition
   4. Assign a non-rootfs mount point to the partition, choosing ext4 fs type
   5. Complete installation
   6. Reboot into post-install system

Expected Results

   *  installation completes successfully
   * post-installation system boots
   * ext4 filesystem is correctly identified and mounted

---

Test Case: Create new ext4 partition (root fs) How to Test:

   1. Boot the installer
   2. Advance to the (ddruid) partitioning screen
   3. Create a new (or use existing) ext3 partition for /boot
   4. Create a new (or use existing) partition
   5. Assign a rootfs mount point to the partition, choosing ext4 fs type
   6. Complete installation
   7. Reboot into post-install system

Expected Results:

   * installation completes successfully
   * post-installation system boots
   * ext4 filesystem is correctly identified and mounted

---

Test Case: ext4 fs on LVM LV How to Test:

   1. Boot the installer
   2. Advance to the (ddruid) partitioning screen
   3. Create a new (or use existing) LVM PVs
   4. Create an LVM LV using the PVs
   5. Assign a non-/boot mount point to the LVM LV, choosing ext4 fs type
   6. Complete installation
   7. Reboot into post-install system

Expected Results

   * installation completes successfully
   * post-installation system boots
   * ext4 filesystem is correctly identified and mounted using LVM LV device

---

Test Case: rescue mode How to Test:

   1. Boot the installer
   2. Advance to the (ddruid) partitioning screen
   3. Create a new (or use existing) ext4 partition and assign a non-/boot mount point
   4. complete installation
   5. reboot into post-install system using rescue mode

Expected Results:

   * installation completes successfully
   * installation enters rescue mode
   * rescue mode detects and mounts ext4 partition successfully
   * user can interact with ext4 filesystem (read, write & edit files) 

---

Test Case: ext4 native (non-LVM) How to Test:

   1. Boot the installer
   2. Advance to the (ddruid) partitioning screen
   3. Create a new non-LVM ext4 partition and assign to / mount point
   4. complete installation

Expected Results

   * installation completes successfully
   * post-installation system boots
   * ext4 filesystem is correctly identified and mounted

---

DRAFT

Perhaps we should script all the changes and let the tester just run the script

su -c 'chmod +x /home/<user>/Download/Bootchart-test.sh && /home/<user>/Download/Bootchart-test.sh 

Draft Continue

Have to hear from Harald how he wants it should be something like this..

Use a live cd or make a default all install.

Open a terminal window and run:

su -c 'yum -y install bootchart'

Open /sbin/bootchartd with your favourite text editor and change line 121

From

local exit_proc="gdmgreeter gdm-binary kdm-greet kdm ldm"

To

local exit_proc="firefox"

Or open up a terminal window and run

su -c 'sed 's/gdmgreeter\ gdm-binary\ kdm-greet\ kdm\ ldm/firefox/g' File > File 

Open /etc/bootchartd.conf with your favourite text editor and change line 13

From

SAMPLE_PERIOD=0.2

To

SAMPLE_PERIOD=20

Or open up a terminal window and run

su -c 'sed 's/0.2/20/g' File > File 

Auto logon?

Perhaps Harald wants the user auto logon and auto start firefox ??

Bootcharts

1. TODO

We need to figure out were we want the tester to upload the bootchart.. We need to coordinate with the kernel guy's and rel-eng to provide the kernel with debug turned off and rel-eng to build a testable test images for that test day..

Please record information about you and your bootup time in the table below.

Test Case 1	Pass	Bug Number
User:johannbg
User:jlaska		12345
User:wwoods		56789

Test Case 2	Pass	Bug Number
User:johannbg		12345
User:jlaska
User:wwoods		56789

Test Case 3	Pass	Bug Number
User:johannbg		12345
User:jlaska		56789
User:wwoods

Need help?

We'll have a host of QA and Development characters hanging out discussing bugs (aka "features"), expectations, and test areas. I've included details below for how you can contribute below.

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

• Development - User:Sandeen
• Quality Assurance - User:Johannbg, User:jlaska, User:wwoods

Want to join in?
If you'd like to sign up to help field questions, please add your name to the list above.