Ankursinha (talk | contribs) |
|||
| Line 47: | Line 47: | ||
== Test Results == | == Test Results == | ||
If you have problems with any of the tests,please report a bug to [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=livecd-tools Bugzilla for livecd-tools] . 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, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line. | If you have problems with any of the tests,please report a bug to [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=livecd-tools Bugzilla for livecd-tools] or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=liveusb-creator Bugzilla for liveusb-creator] . 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, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line. | ||
{| | {| | ||
Revision as of 18:48, 19 April 2012
| Fedora Test Days | |
|---|---|
| |
| livecd-tools | |
| Date | <<04-19-2012>> |
| Time | all day |
| Website | QA/Fedora_17_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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 installment of Fedora Test Day will focus on livecd-tools and creating a Fedora USB installation stick via the command-line with livecd-tools' livecd-iso-to-disk on Fedora 16, 17, and with liveusb-creator on Fedora and Windows.
Who's available
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - FranciscoD (FranciscoD)
- Quality Assurance - vicodan (vicodan)
Prerequisite for Test Day
- A Fedora 16/17 installation. (or a windows installation)
- Time
- Usb key(s)
- ISO images of latest Fedora 17 beta. ISO images are here
- Free space on HD (A separate test system would be preferred)
- (optional) Your hardware profile uploaded to Smolt according to these instructions
- (optional) Beer (if you're adult)
- (optional) Hot dogs!
Update your machine
- You need to have the livecd-tools version 16.11 at least.
How to test?
- Please use the process detailed on the How_to_create_and_use_Live_USB wiki page.
- You can use qemu/qemu-kvm to test your live media
qemu -hda /dev/sdX # with more mem if you want to use it instead of just see if it boots
Test Results
If you have problems with any of the tests,please report a bug to Bugzilla for livecd-tools or Bugzilla for liveusb-creator . 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, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.
