From Fedora Project Wiki
m (wiki cleanup) |
(Update template) |
||
| Line 3: | Line 3: | ||
| DATE || TIME || WHERE | | DATE || TIME || WHERE | ||
|- | |- | ||
| | | '''<<FIXME>>''' || From ''12:00'' to ''21:00'' UTC (8am -> 5pm EDT) || [irc://irc.freenode.net/fedora-qa #fedora-qa]) | ||
|- | |- | ||
|} | |} | ||
| Line 9: | Line 9: | ||
=== What to test? === | === What to test? === | ||
Today's installment of Fedora Test Day will focus on | Today's installment of Fedora Test Day will focus on '''<<FIXME>>''' | ||
=== Who's available === | === Who's available === | ||
| Line 28: | Line 26: | ||
* Free space on HD | * Free space on HD | ||
* Rawhide Fully updated | * Rawhide Fully updated | ||
=== How to test? === | === How to test? === | ||
| Line 39: | Line 35: | ||
* How to report back results | * How to report back results | ||
=== Test Cases | === Test Cases === | ||
Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see [[:Category:Test_Cases]]. | |||
=== Test Results === | |||
Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. For example: | |||
{| | |||
! User | |||
! Smolt Profile | |||
! [[QA:Testcase_sample_1|Sample test 1]] | |||
! [[QA:Testcase_sample_2|Sample test 2]] | |||
! [[QA:Testcase_sample_3|Sample test 3]] | |||
! [[QA:Testcase_sample_4|Sample test 4]] | |||
! References | |||
|- | |||
| [[User:FasUser]] | |||
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW] | |||
| PASS | |||
| PASS | |||
| FAIL <ref>See {{bz|12345}}</ref> | |||
| PASS | |||
| <references/> | |||
|- | |||
|} | |||
[[Category:Test Days]] | [[Category:Test Days]] | ||
Revision as of 13:58, 7 August 2009
| DATE | TIME | WHERE |
| <<FIXME>> | 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 <<FIXME>>
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - User:Developer1, User:Developer2
- Quality Assurance - User:Tester1, User:Tester2, User:Tester3
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?
- Usb key
- 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
Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases.
Test Results
Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. For example:
| User | Smolt Profile | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
|---|---|---|---|---|---|---|
| User:FasUser | HW | PASS | PASS | FAIL [1] | PASS |