Test Day:2011-03-03 I18n Desktop

Click here to set up this language box

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 ...

• Development - User:Petersen (juhp)
• Quality Assurance - IgorSoares (igorps), He Rui (rhe), A S Alam (Alam)

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) -- F-15-Alpha RC2.
• Unless otherwise noted, you may use nightly Fedora 15 branch install images. Review for information on downloading and installing Branched.
• Optionally, you may download a non-destructive Fedora 15 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.

Test Cases

• QA:Langpack PackageKit Application
• QA:Langpack Yum Application
• QA:Testcase i18n browsers
• QA:Testcase i18n font application
• QA:Testcase i18n input application
• QA:Testcase i18n input method
• QA:Testcase i18n ibus input

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	pass	warn	fail
Hurry				fail
David Ramsey
David Ramsey
Akira TAGOH	inprogress	fail	fail	inprogress	pass	pass	inprogress	inprogress
Tao Wu	pass	fail	fail	fail	pass	pass	fail	inprogress
Vita Humpa	inprogress	inprogress	inprogress	inprogress	inprogress	inprogress	inprogress	inprogress