From Fedora Project Wiki

No edit summary
(added few bug list to test)
Line 48: Line 48:
* [[QA:Testcase i18n ibus input]]
* [[QA:Testcase i18n ibus input]]


<!--
==== Nice to test ====
==== Nice to test ====
Bugs you might hit or additional situations that are nice to test:
Bugs you might hit or additional situations that are nice to test:
-->
 
* [https://bugzilla.redhat.com/show_bug.cgi?id=681805 No group named Chinese-Support exists]
* [https://bugzilla.redhat.com/show_bug.cgi?id=681802 Changing language to Chinese(P.R. of China) results in Chinese(Hong Kong)]
* [https://bugzilla.redhat.com/show_bug.cgi?id=673449 Need to update Rupee symbol for locale file (hi_IN)]
* [https://bugzilla.redhat.com/show_bug.cgi?id=664008 (ml_IN) default font size with all libreoffice GUI (translated) is small as compared to gnome application]
* [https://bugzilla.redhat.com/show_bug.cgi?id=714826 system-config-keyboard never applies changes]
* [https://bugzilla.redhat.com/show_bug.cgi?id=722837 (All langs) gtkhtml-editor-WARNING **:zh-CN: No such language]


== Test Results ==
== Test Results ==

Revision as of 09:33, 29 August 2011

Fedora Test Days
Echo-testing-48px.png
I18n Desktop

Date 2011-09-01
Time all day

Website QA/Fedora_16_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's installment of Fedora Test Day will focus on internationalization support in desktop applications

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

  • One or more keyboards with different layouts.
  • Bare metal or virtual machine.
  • Usb key, a virtualized guest or a burned CD/DVD with the test image

How to test?

Prepare Your System

  • Tests requiring physical media (e.g. DVD or CD images) -- [Link to F-16-Alpha].
  • Unless otherwise noted, you may use nightly Fedora 16 branch install images. Review for information on downloading and installing Branched.
  • Optionally, you may download a non-destructive Fedora 16 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found [ here].

Test Cases

Nice to test

Bugs you might hit or additional situations that are nice to test:

Test Results

If you have problems with any of the tests, report a bug to Bugzilla. For instance file a bug report against the component firefox if you have problems testing the Firefox Web Browser. If you are unsure about exactly how to file the report or what other 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 be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.

User Langpack PackageKit Langpack Yum browsers font application input application input method ibus input Nice to Test References
Sample User
Inprogress inprogress
Pass pass
Warning warn
[1]
Fail fail [2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345