From Fedora Project Wiki

(Add reference bug)
(Adusted the page using current test day template)
Line 2: Line 2:
{{draft}}
{{draft}}


{|border="1"
{{Infobox_group
|-style="color: white; background-color: #3074c2; font-weight: bold"
| name = Fedora Test Days
| DATE || TIME || WHERE
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_15_test_days]]
|-
| caption = I18n Desktop
| '''2011-03-03''' || All Day || [irc://irc.freenode.net/fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| date = '''2011-03-03'''
|-
| time = all day
|}
| website = [[QA/Fedora_15_test_days]]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| fedora_mailing_list = test
}}


{{admon/note | 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 [http://bugzilla.redhat.com 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 - which should be linked at [[QA/Test_Days]] - and see if a similar but more recent Test Day is planned or has already happened.}}
{{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}


== What to test? ==
== What to test? ==
Line 51: Line 54:
== Test Results ==
== Test Results ==


Specific L10N bugs like typos and translation mistakes should be directly reported to the local translation team mailing list or a bug report should be filed at [https://bugzilla.redhat.com/ Bugzilla] against the related language. General bugs that affect all languages like strings not marked for translation, downstream patching that breaks translations and input method issues should be filed against the related package. 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.
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 [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility 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 [[Template:result|result template]] to enter your result, as shown in the example result line.


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. For each test case, if your system worked correctly, simply enter the word '''<nowiki>{{result|pass}}</nowiki>'''. If you had trouble, enter the word '''<nowiki>{{result|warn}}<ref>xxx</ref></nowiki>''' or '''<nowiki>{{result|fail|bug No}}</nowiki>''', with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.


{| class="wikitable sortable" border="1"
{| class="wikitable sortable" border="1"

Revision as of 09:00, 12 February 2011

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

  • Tests requiring physical media (e.g. DVD or CD images) -- [Link_to_alpha download F-15-Alpha].
  • 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

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 Test Description Result References
Sample User Asian Language Install - Chinese
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. ↑ Test pass, but also encountered RHBZ #54321
  2. ↑ RHBZ #12345
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2011-03-03_I18n_Desktop&oldid=220850"