From Fedora Project Wiki

< User:Johannbg‎ | Draft‎ | QA‎ | Test Days

No edit summary
No edit summary
Line 1: Line 1:
{|
! DATE !! TIME !! WHERE
|-
| $Date || From ''$Time'' to ''$Time'' UTC || [irc://irc.freenode.net/fedora-qa #fedora-qa] (need [[QA/Test_Days#Where_are_Test_Days_held.3F|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'''
# Please download a live ISO image for your architecture:
#* [http://download.fedora.redhat.com/pub/fedora/linux/releases/test/11-Alpha/Live/i686 i686]
#* [http://download.fedora.redhat.com/pub/fedora/linux/releases/test/11-Alpha/Live/x86_64 x86_64]
# Prepare your live image by following the instructions at [[FedoraLiveCD]]
# Or run the dowloaded ISO image in qemu: <pre> su -c 'qemu -cdrom Fedora-11-Alpha-i686-Live.iso -m 512 -std-vga'</pre>
'''Install Media'''
# Consult the [http://docs.fedoraproject.org/install-guide/f10/ installation guide] for [http://docs.fedoraproject.org/install-guide/f10/en_US/ch-experts-quickstart.html quick start] information to determine the best install method for your needs.
# Follow [http://docs.fedoraproject.org/install-guide/f9/en_US/ch-other-install-methods.html instructions] for installing your system.
#* Alternatively, on an already installed system:
#*# Install snake: <pre>yum install snake</pre>
#*# Configure your system for installation: <pre>snake-install http://download.fedora.redhat.com/pub/fedora/linux/releases/test/11-Alpha/Fedora/i386/os</pre>
{{User:Robertmwilliams/EXT4InstallationTestPlan}}
{{User:Robertmwilliams/EXT4InstallationTestPlan}}


=== DRAFT ===
Perhaps we should script all the changes and let the tester just
run the script
<pre>su -c 'chmod +x /home/<user>/Download/Bootchart-test.sh && /home/<user>/Download/Bootchart-test.sh </pre>
== 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:
<pre>su -c 'yum -y install bootchart'</pre>
Open /sbin/bootchartd with your favourite text editor and change line 121
From
<pre>local exit_proc="gdmgreeter gdm-binary kdm-greet kdm ldm"</pre>
To
<pre>local exit_proc="firefox"</pre>
Or open up a terminal window and run
<pre>su -c 'sed 's/gdmgreeter\ gdm-binary\ kdm-greet\ kdm\ ldm/firefox/g' File > File </pre>
Open /etc/bootchartd.conf with your favourite text editor and change line 13
From
<pre>SAMPLE_PERIOD=0.2</PRE>
To
<pre>SAMPLE_PERIOD=20</PRE>
Or open up a terminal window and run
<pre>su -c 'sed 's/0.2/20/g' File > File </pre>
== Auto logon? ==
Perhaps Harald wants the user auto logon and auto start firefox ??
== Bootcharts ==
# 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.


{|
{|
Line 127: Line 30:
|
|
|-
|-
| [[User:wwoods]]
| [[User:]]
| align="right" style="background-color: red;" |  
| align="right" style="background-color: red;" |  
| 56789
| 56789
Line 156: Line 59:
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:Sandeen]]
* Development - [[User:Sandeen]]
* Quality Assurance - [[User:Johannbg]], [[User:jlaska]], [[User:wwoods]]
* Quality Assurance - [[User:Johannbg]], [[User:jlaska]], [[User:Robertmwilliams]],


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


[[Category:Test Days]]
[[Category:Test Days]]

Revision as of 18:57, 2 February 2009

Installation Test Plan

In the table below, duplicate the italicized example rows as needed and replace the user and pass or fail with your own user name and results.

User Description How to Test Expected Results Results

Assign ext4 fs with mount point


  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.
  1. ext4 filesystems are recognized.
  2. Mount point can be assigned to ext4 filesystem.
  3. Installation completes successfully.
  4. System starts properly with all filesystems mounted.
user * * * pass
user * * * fail

Create new ext4 partition (non-root fs)


  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
  1. installation completes successfully
  2. post-installation system boots
  3. ext4 filesystem is correctly identified and mounted
user * * * pass
user * * * fail

Create new ext4 partition (root fs)


  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
  1. installation completes successfully
  2. post-installation system boots
  3. ext4 filesystem is correctly identified and mounted
user * * * pass
user * * * fail

Identify ext4 filesystems


  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.
  1. Anaconda starts successfully.
  2. ext4 filesystems are detected and listed in partition layout of Disk druid screen.
  3. Disk druid allows basic manipulation with ext4 filesystems.
user * * * pass
user * * * fail

ext4 fs on LVM LV


  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
  1. installation completes successfully
  2. post-installation system boots
  3. ext4 filesystem is correctly identified and mounted using LVM LV device.
user * * * pass
user * * * fail

ext4 native (non-LVM)


  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
  1. installation completes successfully
  2. post-installation system boots
  3. ext4 filesystem is correctly identified and mounted
user * * * pass
user * * * fail

Mount and recover ext4 partitions from rescue mode


  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
  1. installation completes successfully
  2. installation enters rescue mode
  3. rescue mode detects and mounts ext4 partition successfully
  4. user can interact with ext4 filesystem (read, write & edit files)
user * * * pass
user * * * fail

Ext 4 fs encrypted


  1. Boot the installer
  2. Advance to the (ddruid) partitioning screen
  3. Create a new (or use existing) partition
  4. Assign a non-/boot mount point to the LVM LV, choosing ext4 fs type
  5. select "encrypt" for the partition
  6. complete installation
  7. reboot into post-install system
  1. installation completes successfully
  2. post-installation system boots
  3. ext4 filesystem is correctly identified as encrypted block device and mounted
  4. ext4 filesystem entry is present in /etc/crypttab
user * * * pass
user * * * fail

Exploratory Test Plan

If you perform an EXT4 installation test not in the list above (and feel free to) please enter the information here. We will incorporate selected tests in future test plans.

User Description How to Test Expected Results Results Notes
who am I summary what I did what should happen what did happen (pass/fail) notes or observations
cww PXE boot/setup ext4 in LVM and native partitions Start install via PXE, setup / as ext4 via LVM and /export as ext4 via a native partition Install should complete successfully Install completed successfully, PXE worked just fine. Both / and /export mounted post install and can been accessed via rescue mode Tested on i386


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:]] 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 ...

Idea.png
Want to join in?
If you'd like to sign up to help field questions, please add your name to the list above.
Retrieved from "https://fedoraproject.org/w/index.php?title=User:Johannbg/Draft/QA/Test_Days/Features/EXT4&oldid=75675"