From Fedora Project Wiki

m (QA/Test Days/2009-04-09 moved to Test Day:2009-04-09 UEFI: Use new test day namespace)
m (Start with a few basic test case stubs)
Line 77: Line 77:
  
 
Perform each of the following test cases:
 
Perform each of the following test cases:
# [[QA:Testcase_UEFI_test1| Sample Test #1 ]]
+
# [[QA:Testcase_UEFI_boot.iso]]
# [[QA:Testcase_UEFI_test2| Sample Test #2 ]]
+
# [[QA:Testcase_UEFI_efidisk.img]]
# [[QA:Testcase_UEFI_test3| Sample Test #3 ]]
+
# [[QA:Testcase_UEFI_pxeboot]]
# [[QA:Testcase_UEFI_test4| Sample Test #4 ]]
 
  
 
=== Report your results ===
 
=== Report your results ===

Revision as of 20:01, 3 April 2009

What to test?

Today's installment of Fedora Test Day will focus on Features/EFI. The objective is to verify that affected components (ie, grub, kernel, efibootmgr) provide the expected UEFI functionality on appropriate hardware (ie, it locates devices, installs, and boots). Fedora 11's UEFI 2.1 implementation has been tested on Intel UEFI-capable systems only; those with access to other vendors UEFI-capable systems are actively solicited to validate their hardware.

Supported Architectures currently are X86 and X86_64. No Fedora 11 compose of IA64 is available.

Who's available

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

Person Timezone
Peter Jones (developer) UTC-4
Brian Maly (developer) UTC-4
Bhavna Sarathy (developer) UTC-4
James Laska (tester) UTC-4
Chris Ward (tester) UTC+2
Liam (tester) UTC+8


Normal practice is to find these people on #fedora-qa for assistance. Note that these folks are based in the eastern US and in Brno, Czech Republic. We are trying to find coverage for other timezones such as China, India. Testers in those locations can send questions by email if help is not available on IRC.

What's Needed To Test

Required for testing Features/EFI:

Optional but recommended for testing Features/EFI:

  • FAS Account - you can create an account in 3 minutes if you don't have one. This account lets you make non-anonymous contributions to the Fedora wiki.
  • Your hardware profile uploaded to Smolt according to these instructions
Stop (medium size).png
Rawhide is raw
Rawhide is a development branch of Fedora. While changes to Fedora post-beta are limited, it is advised you back up your data before participating.


Warning.png
FIXME
How to identify if your system supports UEFI?

How To Test

Testing will require using a system running Rawhide. There are several methods available for updating your system to rawhide. The following sections outline two methods.

Update your machine

See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide.

Live Image

Alternatively, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture MD5SUM
i386 f5852f27e324fb87f4d060abf44d16dc
x86_64 195e48300a94c65289ffdb20d4eeb2d4


Note.png
Latest syslinux package?
Creating a LiveUSB of this rawhide image requires the latest version of syslinux, which is currently available in Rawhide and in the latest Windows liveusb-creator. Users of F10 and below can upgrade to the latest syslinux package using
yum --enablerepo=rawhide update syslinux
.

Filing Bugs

All bugs will be tracked in Bugzilla. To file a bug found testing Features/EFI, click here

Testing

Perform each of the following test cases:

  1. QA:Testcase_UEFI_boot.iso
  2. QA:Testcase_UEFI_efidisk.img
  3. QA:Testcase_UEFI_pxeboot

Report your 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, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below.

The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to your Smolt hardware profile (see above for a link with instructions on submitting your hardware profile to Smolt). For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, as a link to the bug report for the failure. If you could not perform one test (for example, you cannot perform the more advanced tests because the basic one fails, or you cannot perform the multihead test as you have only one display), enter the word N/A. In the comments column, enter any additional information that is related to your testing.

Results

User Smolt Profile Test #1 Test #2 Test #3 Test #4 Comments
User:SampleUser