Test Day:2013-05-02 Internationalization

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Created Page for Fedora 19 i18n Test Day)
 
(Added missing category)
(13 intermediate revisions by 7 users not shown)
Line 34: Line 34:
 
=== Prepare Your System ===
 
=== Prepare Your System ===
  
* Tests requiring ''physical media'' (e.g. DVD or CD images) and the latest version of packages from updates/updates-testing: [LINK HERE].
+
* Tests requiring ''physical media'' (e.g. DVD or CD images) and the latest version of packages from updates/updates-testing: [http://dl.fedoraproject.org/pub/alt/stage/19-Beta-TC2/Live/ Pre-Release Fedora 19 Beta (tc2)].
* You may download a non-destructive Fedora 19 live image for your architecture. The specific live image for I18N tests can be found [LINK '''here''']. Tips on using a live image are available at [[FedoraLiveCD]]
+
 
 
* Unless otherwise noted, you may use nightly Fedora 19 ''branch'' install images.  [[Releases/Branched|Review for information on downloading and installing Branched]].
 
* Unless otherwise noted, you may use nightly Fedora 19 ''branch'' install images.  [[Releases/Branched|Review for information on downloading and installing Branched]].
  
=== Test Cases ===
+
=== Test Cases and Results ===
  
* [[QA:Langpack Yum Application]]
+
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. For instance file a bug report against the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=17&component=firefox 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 separate pages by testing categories below.
* [[QA:Testcase i18n browsers]]
+
 
* [[QA:Testcase i18n font application]]
+
* [[{{FULLPAGENAME}}/Results/Input_overall|Input (overall)]]
* [[QA:Testcase i18n ibus input]]
+
* [[{{FULLPAGENAME}}/Results/Input_lang|Input (language-specific)]]
* [[QA:Gnome Input Method Integration IBus]]
+
* [[{{FULLPAGENAME}}/Results/Rendering|Rendering]]
* [[QA:Testcase ibus-typing-booster]]
+
* [[{{FULLPAGENAME}}/Results/Printing|Printing]]
* [[QA:Inscript2 Keymaps]]
+
* [[{{FULLPAGENAME}}/Results/Other|Other]]
* [[QA:Intelligent Pinyin]]
+
* [[QA:Eekboard]]
+
* [[QA:Testcase Fonts HarfbuzzNG]]
+
* [[QA:Font Configuration Tool]]
+
  
 
==== Nice to test ====
 
==== Nice to test ====
Line 80: Line 76:
 
* [https://bugzilla.redhat.com/show_bug.cgi?id=722837 (All langs) gtkhtml-editor-WARNING **:zh-CN: No such language]
 
* [https://bugzilla.redhat.com/show_bug.cgi?id=722837 (All langs) gtkhtml-editor-WARNING **:zh-CN: No such language]
  
== Test Results ==
+
[[Category:Test Days]] [[Category:Fedora 19 Test Days]]
 
+
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. For instance file a bug report against the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=17&component=firefox 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 [[Template:result|result template]] to enter your result, as shown in the example result line.
+
 
+
 
+
{| class="wikitable sortable" border="1"
+
 
+
! User
+
! [[QA:Langpack Yum Application|yum-langpacks]]
+
! [[QA:Testcase i18n browsers|browsers]]
+
! [[QA:Testcase i18n font application|font apps]]
+
! [[QA:Testcase i18n ibus input|ibus input]]
+
! [[QA:Gnome Input Method Integration IBus|IBus GNOME]]
+
! [[QA:Testcase ibus-typing-booster|ibus-typing-booster]]
+
! [[QA:Inscript2 Keymaps|Inscript2]]
+
! [[QA:Intelligent Pinyin|Pinyin]]
+
! [[QA:Eekboard|eekboard]]
+
! [[QA:Testcase Fonts HarfbuzzNG|harfbuzz]]
+
! [[QA:Font Configuration Tool|Font Configuration Tool]]
+
! [[Test_Day:2011-03-03_I18n_Desktop#Nice_to_test|Nice to Test]]
+
! References
+
|-
+
| [[User:SampleUser|Sample User]]
+
| {{result|none}}
+
| {{result|none}}
+
| {{result|pass}}
+
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
+
| {{result|fail||12345}}
+
| {{result|none}}
+
| {{result|inprogress}}
+
| {{result|none}}
+
| {{result|none}}
+
| {{result|none}}
+
| {{result|none}}
+
| {{result|none}}
+
| <references/>
+
|}
+
 
+
[[Category:Fedora 19 Test Days]]
+

Revision as of 12:34, 16 May 2013

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

Date 2013-05-02
Time all day

Website QA/Fedora_19_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 internationalization support in desktop applications

Who's available

The following cast of characters will be available for 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 and 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 separate pages by testing categories below.

Nice to test

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