No edit summary |
|||
| Line 41: | Line 41: | ||
== Test Results == | == Test Results == | ||
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=preupgrade preupgrade]. If you are unsure about exactly how to file the report or what 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 describe the hardware (monitor, and optionally printer, scanner and colorimeter) you used to test. For each test case, if your system worked correctly, simply enter the word ''' | If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=preupgrade preupgrade]. If you are unsure about exactly how to file the report or what 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 describe the hardware (monitor, and optionally printer, scanner and colorimeter) you used to test. For each test case, if your system worked correctly, simply enter the word '''<nowiki>{{result|pass}}</nowiki>'''. If you had trouble, enter the word '''<nowiki>{{result|warn}}<ref>xxx</ref></nowiki>''' or '''<nowiki>{{result|fail|bug No}}</nowiki>''', with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash. | ||
{| | {| | ||
Revision as of 06:41, 18 August 2010
It is still under construction and content may change. Do not rely on the information on this page.
| DATE | TIME | WHERE |
| 2010-09-02 | All day | #fedora-test-day (webirc) |
What to test?
Today's installation of Fedora Test Day will focus on Preupgrade
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Richard Hughes (IRC: hughsie)
- Quality Assurance - He Rui (IRC: rhe)
Prerequisite for Test Day
- A F12 or F13 system on bare metal or virtual machine
- Network connection
- The following packages updates installed
How to test?
Follow the test cases below to preupgrade your existing fedora 12 or 13 system.
Test Cases
Test Results
If you have problems with any of the tests, report a bug to Bugzilla usually for the component preupgrade. If you are unsure about exactly how to file the report or what 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 describe the hardware (monitor, and optionally printer, scanner and colorimeter) you used to test. For each test case, if your system worked correctly, simply enter the word {{result|pass}}. If you had trouble, enter the word {{result|warn}}<ref>xxx</ref> or {{result|fail|bug No}}, with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.
| User | Smolt Profile | preupgrade | preupgrade older release | preupgrade-cli | References |
|---|---|---|---|---|---|
| User:Example | HW |  |
 |
