From Fedora Project Wiki
No edit summary |
m (add todo) |
||
| Line 16: | Line 16: | ||
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ... | The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ... | ||
* Development - [[User:harald | Harald Hoyer | * Development - [[User:harald|Harald Hoyer]] | ||
* Quality Assurance - [[User:Jlaska | James Laska]], [[User:Johannbg | Jóhann B.]] | * Quality Assurance - [[User:Jlaska|James Laska]], [[User:Johannbg|Jóhann B.]] | ||
=== Prerequisite for Test Day === | === Prerequisite for Test Day === | ||
| Line 39: | Line 39: | ||
=== Test Cases and Results === | === Test Cases and Results === | ||
{{admon/note|FIXME|Test cases coming soon ...}} | |||
[[Category:Test Days]] | [[Category:Test Days]] | ||
Revision as of 12:43, 18 August 2009
| DATE | TIME | WHERE |
| Thu August 27, 2009 | From 12:00 to 21:00 UTC (8am -> 5pm EDT) | #fedora-qa) |
What to test?
Today's installment of Fedora Test Day will focus on:
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Harald Hoyer
- Quality Assurance - James Laska, Jóhann B.
Prerequisite for Test Day
List any prerequisite needs for the test event. A fresh system, virtualized guest, a blank DVD ... a desire to break software?
- Enough free space on /boot
- Usb externally connected HD IDE/SATA
- Empty HD IDE/SATA/SCSI
- Free space on HD
- Rawhide Fully updated
How to test?
High level details on how a contributor can get involved. This can include (but not limited to):
- Areas to target with exploratory testing
- A list of pre-defined test cases to execute
- How to report back results
Test Cases and Results
FIXME
Test cases coming soon ...
Test cases coming soon ...