Test Day:2011-09-22 I18n Desktop

From FedoraProject

Revision as of 01:18, 22 September 2011 by Tagoh (Talk | contribs)

Jump to: navigation, search
Warning (medium size).png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
Fedora Test Days
Echo-testing-48px.png
I18n Desktop

Date 2011-09-22
Time all day

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

Mailing list
MailSubscribeArchives


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.

Contents

What to test?

Today's installment of Fedora Test Day will focus on input methods support in desktop applications regarding new features developed during Fedora 16 development cycle.

Who's available

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

  • Development -
  • Quality Assurance -

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-16-Beta RC1.
  • 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.
  • Please make sure if the above media has the latest ibus. running yum update or yum update ibus would be nice prior to begin.

Test Cases


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 ibus start ibus bridge hotkey ibus GNOME Shell 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