From Fedora Project Wiki
| DATE | TIME | WHERE |
| Tue April 14, 2009 | All day | #fedora-qa) |
What to test?
Today's installment of Fedora Test Day will revisit:
Who's available
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development
- Quality Assurance
What's needed to test
Required for testing:
- Rawhide or Fedora 11 Beta fully updated.
- A system capable of testing Features/EFI support
- A Red Hat Bugzilla account.
Optional but recommended for testing:
- 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
.png){kind=small}
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.
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.
How to test?
Update your machine
See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Live Image
Optionally, you may download a rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
| Architecture | MD5SUM |
|---|---|
| Coming soon | Coming soon |
| x86_64 | c3582375fda8c0103a77e6a1c482e56a |
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
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.
Test
The following test cases are designed to stress the installer auto-partitioning:
- QA:Testcase Anaconda autopart_install
- QA:Testcase Anaconda autopart_(encrypted)_install
- QA:Testcase Anaconda autopart_(shrink)_install
- QA:Testcase Anaconda autopart_(use free space)_install
- QA:Testcase Anaconda autopart with dmraid
- QA:Testcase Anaconda autopart with iSCSI (no authentication)
The following test cases validate different software raid scenarios:
- QA/TestCases/PartitioningUsrOnRaid0
- QA/TestCases/PartitioningRootfsOnRaid1
- QA/TestCases/PartitioningUsrOnRaid5
- QA/TestCases/PartitioningUsrOnRaid6
- QA/TestCases/PartitioningRaid0OnLvmDevice
- QA/TestCases/PartitioningPreExistingRaidRaid
Report your results
- If you experience any unexpected outcomes or failures while executing 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, typically in the format [[User:FasName]]
- The second should be a link to your Smolt hardware profile (see #What.27s_needed_to_test for details)
- For each test case, refer to the test case instructions for details
- Finally, the last column is available for any general comments or concerns not eddress
Results
| User | Smolt Profile | autopart | autopart (luks) | QA:Testcase_test3 | QA:Testcase_test4 | QA:Testcase_test5 | Comments |
|---|---|---|---|---|---|---|---|
| User:SampleUser | |||||||
| User | Smolt Profile | autopart | autopart (luks) | QA:Testcase_test3 | QA:Testcase_test4 | QA:Testcase_test5 | Comments |