From Fedora Project Wiki
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


Important.png
Usability feedback submitted after the Test Day is still valuable
You don't have to test everything in one day. Feedback from Usablility Testing is being collected until Sunday, May 26th 2013 (inclusive). Feel free to submit your feedback anytime before this date.
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. This event covers the advanced storage setup as well as several important usability test scenarios.

If you'll decide to participate in both Usability Testing as well as in Advanced Storage Testing it would be better to start with Usability test cases.

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 Netinst CD (313M) or full DVD (4.2G).
  • 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

# 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.

Test cases for usability test day are located at QA:2013-05-21_Anaconda_usability_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.

Anaconda usability

Test Case Participants
Please fill in only participant nick/name. For the results use [1]
1. Text mode installation (anaconda-text-1)
none
Warning warn mbanas [1] [2] [3]
Warning warn mbanas [4] [5] [6]
Warning warn mbanas [7] [8]
Pass pass pkotvan
Pass pass pholica
Pass pass lnovy
Warning warn mganisin [9] [10]
Pass pass nonamedotc
Pass pass jbastian [11]
2. Create multiple Volume Groups (anaconda-lvm-1)
none
Fail fail pkotvan
none mbanas
Warning warn lnovy [12] [13]
none mganisin
Pass pass jbastian
Pass pass pholica [14]
3. iSCSI target is part of LVM Volume Group (anaconda-lvm-2)
none
none mbanas
none mganisin
4. LVM on top of RAID (anaconda-lvm-3)
Pass pass pkotvan
Fail fail pholica
none mbanas
Pass pass lnovy
5. CHAP authentication against iSCSI target (anaconda-iscsi-1)
none mbanas
Inprogress inprogress pkotvan
6. Search for specific device (anaconda-storage-1)
none
none mbanas
  1. RHBZ #965460
  2. RHBZ #965477
  3. RHBZ #965498
  4. RHBZ #965509
  5. RHBZ #965526
  6. RHBZ #965543
  7. RHBZ #965561
  8. RHBZ #965571
  9. RHBZ #965580
  10. RHBZ #965592
  11. RHBZ #965774
  12. RHBZ #965623
  13. RHBZ #965660
  14. RHBZ #965805

Advanced Storage

Note.png
Feedback about Usability is Welcome
There are also special usability oriented test cases above, however you can fill usability report also for following test cases. If you would like to share your experience, please do it in this form once you'll complete a test case.
Test Case Tester(s)/Results
1. Installation on bios/firmware RAID
none
2. Installation on iSCSI
none
Pass pass mbanas
Warning warn mganisin [1] [2]
3. Default LVM with encryption
Pass pass nonamedotc
Pass pass mbanas
Pass pass mganisin
4. Reuse /home on LVM
Pass pass nonamedotc
Pass pass mbanas
5. More disks
none
Pass pass mbanas
6. Separate mountpoints
Pass pass nonamedotc
Pass pass mbanas
7. Reuse existing VG
none
Warning warn mbanas [3]
8. LVM on top of sw RAID
none
Pass pass mbanas
9. Reuse encrypted partitions
none
Warning warn mbanas [4]
10. Create multiple VGs
none
Pass pass mbanas
Warning warn jstodola [5]
Just An Example
Pass pass john doe
Inprogress inprogress j.doe
Fail fail jane doe [6] [6]
Warning warn jdoe
[7]
  1. RHBZ #965736
  2. RHBZ #965703
  3. RHBZ #965752
  4. RHBZ #965754
  5. RHBZ #965755
  6. 6.0 6.1 RHBZ #1
  7. Brief description about the warning status