From Fedora Project Wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
{|border="1" | |||
|-style="color: white; background-color: #3074c2; font-weight: bold" | |||
| DATE || TIME || WHERE | |||
|- | |||
| '''<<FIXME>>''' || From ''12:00'' to ''21:00'' UTC (8am -> 5pm EDT) || [irc://irc.freenode.net/fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) | |||
|- | |||
|} | |||
=== What to test? === | |||
Today's installment of Fedora Test Day will focus on '''i18n''' | |||
=== Who's available === | |||
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ... | |||
* Development - [[User:Petersen]], | |||
* Quality Assurance - | |||
=== 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 | |||
* 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 === | |||
''<<FIX ME>>''[[:Category:Test_Cases]]. | |||
* [[QA:Testcase_i18n_font_desktop]] | |||
* [[QA:Testcase_i18n_in_application]] | |||
* [[QA:Testcase i18n browsers]] | |||
* [[QA:Testcase ibus input]] | |||
* [[QA:Testcase ibus start]] | |||
* [[QA:Testcase imsettings enable]] | |||
=== 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: | |||
[[Category:Test Days]] [[Category:Proposed_Test_Days]] |