From Fedora Project Wiki

Line 91: Line 91:
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|pass}}
| {{result|pass}} <ref>tested on ja_JP</ref>
| {{result|pass}}
| {{result|pass}} <ref>tested on ja_JP</ref>
| {{result|pass}}
| {{result|pass}} <ref>tested on ja_JP</ref>
| {{result|inprogress}}
| {{result|inprogress}}
| <references/>
| <references/>

Revision as of 10:41, 1 September 2011

Fedora Test Days
I18n Desktop

Date 2011-09-01
Time all day

Website QA/Fedora_16_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:

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
User:Tagoh
Pass pass
Fail fail
[1]
Pass pass
Fail fail
[2]
Inprogress inprogress
Inprogress inprogress
Pass pass
[3]
Pass pass
[4]
Pass pass
[5]
Inprogress inprogress
  1. langpack-ja for libreoffice isn't pulled in RHBZ #734976
  2. langpack-ja for libreoffice isn't pulled in RHBZ #734976
  3. tested on ja_JP
  4. tested on ja_JP
  5. tested on ja_JP
Igor Soares
Fail fail
[1]
Fail fail
[2]
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
  1. Encountered RHBZ #734976
  2. Encountered RHBZ #734976
Antonio Trande
Pass pass
Pass pass
Pass pass
Pass pass
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress