From Fedora Project Wiki
No edit summary |
|||
| Line 3: | Line 3: | ||
| DATE || TIME || WHERE | | DATE || TIME || WHERE | ||
|- | |- | ||
| '''2009-10-29''' || | | '''2009-10-29''' || Daytime US EDT and Asia-Pacific Daytime || [irc://irc.freenode.net/fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) | ||
|- | |- | ||
|} | |} | ||
=== What to test? === | === What to test? === | ||
Today's installment of Fedora Test Day will focus on '''i18n''' | Today's installment of Fedora Test Day will focus on '''i18n''' | ||
=== Who's available === | === Who's available === | ||
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:Petersen|Jens Petersen]] (juhp), | * Development - [[User:Petersen|Jens Petersen]] (juhp), [[User:Dchen|Ding-Yi Chen]], | ||
* Quality Assurance - [[User:Rhe|He Rui]], [[User:Aalam|Alam]] | * Quality Assurance - [[User:Rhe|He Rui]], [[User:Aalam|Alam]] | ||
| Line 22: | Line 20: | ||
=== How to test? === | === How to test? === | ||
The idea is to test common actions in desktop applications | The idea is to test common actions in desktop applications using your native language. | ||
It is better to start testing with a fresh account or Live instance (without persistence). | It is better to start testing with a fresh account or Live instance (without persistence). | ||
The main focus areas are: | The main focus areas are: | ||
* | * display of text in browser, openoffice, etc | ||
* input | * input using ibus | ||
* printing | * printing | ||
Revision as of 06:59, 27 October 2009
| DATE | TIME | WHERE |
| 2009-10-29 | Daytime US EDT and Asia-Pacific Daytime | #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 - Jens Petersen (juhp), Ding-Yi Chen,
- Quality Assurance - He Rui, Alam
Prerequisite for Test Day
- Usb key, or
- Rawhide Fully updated
How to test?
The idea is to test common actions in desktop applications using your native language. It is better to start testing with a fresh account or Live instance (without persistence).
The main focus areas are:
- display of text in browser, openoffice, etc
- input using ibus
- printing
Test Cases
- QA:Testcase_i18n_font_desktop
- QA:Testcase_i18n_font_application
- QA:Testcase_i18n_input_application
- QA:Testcase_i18n_browsers
- QA:Testcase_i18n_ibus_input
- QA:Testcase_i18n_input_method
Test Results
Problems identified
Using your own test scenarios, or any of the test cases listed above, please outline problems/failures you encounter using the table below.
| Tester | Language | Desktop | Application Problems | Bug references |
|---|---|---|---|---|
| Tester | Language | Desktop | Application Problems | Bug reference(s) |
Just worked
Provide a list of tests or scenarios that behaved flawlessly.
| Tester | Language | Desktop | Applications tested |
|---|---|---|---|
| Tester | Language | Desktop | Applications tested |