#260: Cover USB-written images better in installation validation testing
-----------------------+-----------------------
Reporter: adamwill | Owner: jskladan
Type: task | Status: new
Priority: major | Milestone: Fedora 17
Component: Wiki | Version:
Resolution: | Keywords:
Blocked By: | Blocking:
-----------------------+-----------------------
Comment (by adamwill):
Okay, this is my take on the cases we need to consider:
QA:Testcase_Boot_Methods_Boot_Iso
QA:Testcase_Boot_Methods_Dvd
QA:Testcase_Live_Image_Boot
QA:Testcase_install_repository_Mirrorlist_default
QA:Testcase_install_repository_DVD_default
QA:Testcase_install_repository_Live_Image
These are obviously critical: we really kinda need all possible
combinations there. We need to test whether the boot.iso, DVD ISO and live
ISOs boot when written to CD/DVD *or* USB, and in each case, we need to
test both BIOS and EFI. In each case, we need to be sure the image boots
and a straight-through installation works.
QA:Testcase_Anaconda_autopart_install
For EFI installs we need to make sure anaconda handles the EFI system
partition differently (this differs from a non-EFI install). For USB
installs we need to make sure the USB stick you're installing from is
correctly filtered out: it's not used as an install target or a potential
bootloader location. So this test is significant to both.
QA:Testcase_Anaconda_Upgrade_New_Bootloader
QA:Testcase_Anaconda_Upgrade_Skip_Bootloader
QA:Testcase_Anaconda_Upgrade_Update_Bootloader
Similar to above - upgrades can behave differently with USB and EFI
installs, particularly in the area of bootloader management. So we need to
test these.
The simplest thing we can do is just add EFI and USB columns to the table,
with boxes in those columns only for the tests in question, I guess. Other
organization scheme suggestions welcome!
--
Ticket URL: <
https://fedorahosted.org/fedora-qa/ticket/260#comment:5>
Fedora QA <
http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance