From Fedora Project Wiki

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

No edit summary
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{|
== My suggestion the whole testday layout... ==
! 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]]
* The layout "box"


=== What to test? ===
{| border="1"
 
|-style="color: white; background-color: #3074c2; font-weight: bold"
This week's instalment of Fedora Test Day will focus on:
| Test Case || Testers || Pass || Bug Number || Comments
 
|}
* [[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}}
 
=== Installation 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
 
<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
* Column 1 contains link to the test cases
* Column 2 Tester fills in his wiki name
* Column 3 Is filled with cpu architecture on testing platform
* Column 4 Is filled with either red of green
* Column 5 Gives  bug number an url to bugzilla
* Column 6 Testers gives comment on his testing experience.


<pre>su -c 'sed 's/gdmgreeter\ gdm-binary\ kdm-greet\ kdm\ ldm/firefox/g' File > File </pre>
Small sample.


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


From
{| border="1"
 
|-style="color: white; background-color: #3074c2; font-weight: bold"
<pre>SAMPLE_PERIOD=0.2</PRE>
|  Test Case || Tester || Arch || Pass || Bug Number || Comments
 
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.
 
{|
! Test Case 1 || Pass || Bug Number
|-
| [[User:johannbg]]
| align="right" style="background-color: lightgreen;" |
|  
|-  
|-  
| [[User:jlaska]]
| align="center" | [[QA:Assign_ext4_fs_with_mount_point | 1 ]]
| align="right" style="background-color: red;" |  
| [[User:johannbg | Jóhann B.]]  
| i386
| style="background-color: red;" |  
| 12345
| 12345
|-
| We all live in the yellow submarine
| [[User:wwoods]]
| align="right" style="background-color: red;" |
| 56789
|-  
|-  
|}
| align="center" | [[QA:Assign_ext4_fs_with_mount_point | 1 ]]
 
| [[User:jlaska | James Alaska]]
{|
| 64bit
!  Test Case 2 || Pass || Bug Number
| style="background-color: lightgreen;" |  
|  
| The Yellow submarine
|-
|-
| [[User:johannbg]]
| align="center" | [[QA:Assign_ext4_fs_with_mount_point | 1 ]]
| align="right" style="background-color: red;" |
| [[User:Robertmwilliams | Robert M.]]
| 12345
| PPC
|-
| style="background-color: red;" |  
| [[User:jlaska]]
| align="right" style="background-color: lightgreen;" |
|
|-
| [[User:wwoods]]
| align="right" style="background-color: red;" |  
| 56789
| 56789
| The yellow submarine
|-  
|-  
|}
| align="center" | [[QA:TestCases/Create new ext4 partition (non-root fs) | 2 ]]
 
| [[User:johannbg | Jóhann B.]]
{|
| 64bit
!  Test Case 3 || Pass || Bug Number
| style="background-color: lightgreen;" |  
|-
|  
| [[User:johannbg]]  
| We all live in the yellow submarine
| align="right" style="background-color: red;" |  
| 12345
|-  
|-  
| [[User:jlaska]]
| align="center" | [[QA:TestCases/Create new ext4 partition (non-root fs) | 2 ]]
| align="right" style="background-color: red;" |  
| [[User:jlaska | James Alaska]]
| 56789
| PPC
| style="background-color: red;" |  
| 555555
| The yellow submarine
|-
|-
| [[User:wwoods]]
| align="center" | [[QA:TestCases/Create new ext4 partition (non-root fs) | 2 ]]
| align="right" style="background-color: lightgreen;" |  
| [[User:Robertmwilliams | Robert M.]]
| i386
| style="background-color: lightgreen;" |  
|
|
|-
| The yellow submarine
|}
|}
=== 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]]
{{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]]

Latest revision as of 23:07, 2 February 2009

My suggestion the whole testday layout...

  • The layout "box"
Test Case Testers Pass Bug Number Comments
  • Column 1 contains link to the test cases
  • Column 2 Tester fills in his wiki name
  • Column 3 Is filled with cpu architecture on testing platform
  • Column 4 Is filled with either red of green
  • Column 5 Gives bug number an url to bugzilla
  • Column 6 Testers gives comment on his testing experience.

Small sample.


Test Case Tester Arch Pass Bug Number Comments
1 Jóhann B. i386 12345 We all live in the yellow submarine
1 James Alaska 64bit The Yellow submarine
1 Robert M. PPC 56789 The yellow submarine
2 Jóhann B. 64bit We all live in the yellow submarine
2 James Alaska PPC 555555 The yellow submarine
2 Robert M. i386 The yellow submarine