From Fedora Project Wiki

No edit summary
Line 141: Line 141:
| {{result|pass}}
| {{result|pass}}
| {{result|fail}}
| {{result|fail}}
| {{result|inprogress}}
| <references/>
|-
| [[User:Vhumpa|Vita Humpa]]
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| <references/>
| <references/>

Revision as of 13:50, 3 March 2011

Fedora Test Days
I18n Desktop

Date 2011-03-03
Time all day

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


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

Test Cases

Nice to test

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

RHBZ #669481

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. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:

If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. 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
Hurry
Fail fail [1] [2]
  1. RHBZ #681802
  2. RHBZ #681805
David Ramsey [1]
  1. Asian Language Install - Japanese i686 system
David Ramsey [1]
  1. Asian Language Install - Japanese x86_64 system
Akira TAGOH
Inprogress inprogress
Fail fail

[1]

Fail fail

[2]

Inprogress inprogress
Pass pass
Pass pass
Inprogress inprogress
Inprogress inprogress
  1. "yum groupinstall kde-desktop" doesn't pull kde-l10n-* in RHBZ #681747
  2. firefox works, but konqueror doesn't for printing. RHBZ #681782
Tao Wu
Pass pass
Fail fail

[1]

Fail fail

[2]

Fail fail
Pass pass
Pass pass
Fail fail
Inprogress inprogress
  1. fonts are not correctly displayed in some applications. RHBZ #681791
  2. Input does not work correctly for pinyin input-method in Chinese popular IM software QQ.. RHBZ #681810
Vita Humpa
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress