From Fedora Project Wiki

Line 33: Line 33:


== How to test? ==
== How to test? ==
The result table is the
 
All the testing will be driven by result tables below. Just pick up a test case from some table, finish it and report result back to table. If necessary also report bug to bugzilla as mentioned Test Results chapter.


=== Initial setup ===
=== Initial setup ===

Revision as of 10:26, 20 May 2013

Fedora Test Days
Echo-testing-48px.png
AnacondaNewUI Followup

Date 2013-05-21
Time all day

Website QA/Fedora_19_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's instalment of Fedora Test Day will focus on new installer features delivered based on recent activities in [Features/AnacondaNewUI_Followup] Fedora 19 Feature.

Who's available

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

  • Quality Assurance - Marian Ganisin (mganisin), Ladislav Jozsa (ljozsa)

Prerequisite for Test Day

Important.png
Risk of data loss
This test day covers installation testing. Hard drives will be formatted during testing and all data on that drive(s) will be lost
  • Recent installation media.
  • Machine for testing installations. All data will/may be lost on this machine!. Virtual machine is acceptable.
  • Machine providing iSCSI target. Procedure how to setup software iSCSI target in Fedora is included in relevant test case.
  • Multiple disks in test machine for several test cases. Again, virtual machine with more disk images will work.
  • Test machine with BIOS/firmware RAID and few hard drives connected into relevant controller.

How to test?

All the testing will be driven by result tables below. Just pick up a test case from some table, finish it and report result back to table. If necessary also report bug to bugzilla as mentioned Test Results chapter.

Initial setup

  • Prepare installation media available at {URL} according to instructions from Installation Guide
  • Optionally install virtualization support in Fedora:
# yum -y install @virtualization
# service libvirtd start
# cp $FEDORA_ISO /var/lib/libvirt/images/Fedora.iso
  • To start virtual machine you can use this command:
# virt-install --accelerate -n test-machine101 -r 1024 -f /var/lib/libvirt/images/test-machine101.img -s 21 -c /var/lib/libvirt/images/Fedora.iso
  • You can destroy virtual machine right after execution of a test case with these commands:
# virsh destroy test-machine101
# virsh undefine --remove-all-storage test-machine101

Test Cases

All test cases are located at QA:AnacondaNewUI_Advanced_Storage_Test_Plan.

You can use result table(s) below to access particular test case directly.

Test Results

If you have problems with any of the tests, report a bug to Bugzilla. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.

Advanced Storage

Test Case Tester(s)/Results
1. Installation on bios/firmware RAID
none
2. Installation on iSCSI
none
3. Default LVM with encryption
none
4. Reuse /home on LVM
none
5. More disks
none
6. Separate mountpoints
none
7. Reuse existing VG
none
8. LVM on top of sw RAID
none
9. Reuse encrypted partitions
none
10. Create multiple VGs
none
Just An Example
Pass pass john doe
Inprogress inprogress j.doe
Fail fail jane doe [1] [1]
Warning warn jdoe
[2]
  1. 1.0 1.1 RHBZ #1
  2. Brief description about the warning status