From Fedora Project Wiki

(Created page with "{{autolang|base=yes}} {{Infobox_group | name = Fedora Test Days | image = link=QA/Fedora_22_test_days | caption = L10n Desktop | date = '''2015...")
 
m (internal link cleaning)
 
(5 intermediate revisions by 4 users not shown)
Line 7: Line 7:
| date = '''2015-103-17'''
| date = '''2015-103-17'''
| time = all day
| time = all day
| website = [[QA/Fedora_22_test_days]]
| website = [[http://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day Fedora Calendar]]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| fedora_mailing_list = test
| fedora_mailing_list = test
Line 27: Line 27:
== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  


* Bare metal or virtual machine. [https://fedoraproject.org/wiki/Getting_started_with_virtualization Start with Virtualization]
* Bare metal or virtual machine. [[Getting_started_with_virtualization|Start with Virtualization]]
* Usb key, a virtualized guest or a burned CD/DVD with the test image.
* Usb key, a virtualized guest or a burned CD/DVD with the [https://getfedora.org/workstation/prerelease/ F22 Alpha image] or the [http://dl.fedoraproject.org/pub/alt/stage/22_Beta_TC2/Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-22_Beta-TC2.iso testing compose image] if you like.
** that may be not the latest. please check the [http://dl.fedoraproject.org/pub/alt/stage/ place] to see the latest.


== How to test? ==
== How to test? ==
Line 35: Line 36:


* Tests requiring ''physical media'' (e.g. DVD or CD images)  
* Tests requiring ''physical media'' (e.g. DVD or CD images)  
* You may download a non-destructive Fedora 22 live image for your architecture. The specific live image for L10N tests can be found (here). Please note we are providing only x84_64 image for this testing. Tips on using a live image are available at [[FedoraLiveCD]]
* You may download a non-destructive Fedora 22 live image for your architecture. The specific live image for L10N tests can be found [http://alt.fedoraproject.org/pub/alt/stage/22_Beta_TC2/Live/x86_64/ here]. Please note we are providing only x84_64 image for this testing. Tips on using a live image are available at [[FedoraLiveCD]]
* Unless otherwise noted, you may use nightly Fedora 20 ''branch'' install images.  [[Releases/Branched|Review for information on downloading and installing Branched]].
* Unless otherwise noted, you may use nightly Fedora 22 ''branch'' install images.  [[Releases/Branched|Review for information on downloading and installing Branched]].
* If you are using a Alpha or pre-Alpha installation please keep in mind to update your system before running the tests.
* If you are using a Alpha or pre-Alpha installation please keep in mind to update your system before running the tests.


Line 76: Line 77:
The following links helps you to guide to file both l10n and i18n related bugs:-
The following links helps you to guide to file both l10n and i18n related bugs:-


* [http://fedoraproject.org/wiki/L10N#Bug_Reporting.2C_Testing.2C_and_Quality_Assurance Instructions to file l10n bugs]
* [[L10N#Bug_Reporting.2C_Testing.2C_and_Quality_Assurance|Instructions to file l10n bugs]]
* [https://fedoraproject.org/wiki/I18N/Bugs/Guidelines Instructions to file i18n bugs]
* [[I18N/Bugs/Guidelines|Instructions to file i18n bugs]]
* [https://fedoraproject.org/wiki/FLTG/Gnome_bug_filing_instructions Instructions to file GNOME bugs]
* [[FLTG/Gnome_bug_filing_instructions|Instructions to file GNOME bugs]]


{{Admon/tip|Fill one bug report by component and issue|You should fill only one bug report by component and by issue.Be sure to link the report here quickly then, to let people re-use it.}}
{{Admon/tip|Fill one bug report by component and issue|You should fill only one bug report by component and by issue.Be sure to link the report here quickly then, to let people re-use it.}}
Line 92: Line 93:




{{Admon/note|Components are classified project wise|Both FUA and non-FUA will have Fedora and Gnome sections|Gnome bugs can be reported as per instructions provided [https://fedoraproject.org/wiki/Test_Day:2013-10-03_Translation_%28l10n%29?rd=Test_Day:2013-09-26_Translation_%28l10n%29#How_to_file_bugs here].}}
{{Admon/note|Components are classified project wise|Both FUA and non-FUA will have Fedora and Gnome sections|Gnome bugs can be reported as per instructions provided [[Test_Day:2013-10-03_Translation_%28l10n%29?rd=Test_Day:2013-09-26_Translation_%28l10n%29#How_to_file_bugs|here]].}}


'''NOTE:-''' If you find any strings in English, kindly confirm whether its 100% translated in upstream. Link for upstream is provided along with each packages. Accordingly please file your bugs, as in some cases latest translations might not be imported.
'''NOTE:-''' If you find any strings in English, kindly confirm whether its 100% translated in upstream. Link for upstream is provided along with each packages. Accordingly please file your bugs, as in some cases latest translations might not be imported.
Line 192: Line 193:
|}
|}


==[[https://fedoraproject.org/wiki/L10N:Non-FUAs_Application_List Non-FUAs Application List]]==
==[[L10N:Non-FUAs_Application_List|Non-FUAs Application List]]==




[[Category:Test Days]] [[Category:Fedora 22 Test Days]]
[[Category:Fedora 22 Test Days]]

Latest revision as of 21:43, 19 September 2016

Fedora Test Days
L10n Desktop

Date 2015-103-17
Time all day

Website [Fedora Calendar]
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?[edit]

Today's installment of Fedora Test Day will focus on translations availability and accuracy in desktop applications

Who's available[edit]

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

Prerequisite for Test Day[edit]

How to test?[edit]

Prepare Your System[edit]

  • Tests requiring physical media (e.g. DVD or CD images)
  • You may download a non-destructive Fedora 22 live image for your architecture. The specific live image for L10N tests can be found here. Please note we are providing only x84_64 image for this testing. Tips on using a live image are available at FedoraLiveCD
  • Unless otherwise noted, you may use nightly Fedora 22 branch install images. Review for information on downloading and installing Branched.
  • If you are using a Alpha or pre-Alpha installation please keep in mind to update your system before running the tests.

How to run desktop in your language?[edit]

After booting from Live iso:
1. On desktop top right corner click on "Live System User"
2. From menu, select "Settings"
3. In "Settings" window, select "Region and Language"
4. Then in "Region and Language" window, Click on "Language", to add your language click ... (more) sign at the bottom.
5. In window select your language (start type name in English), then select language name and Click Done
6. enable INPUT method, in "Region and Language" window, Click on "Input Method", to add keyboard you want, click on plus ('+') and (more) sign at the bottom.
7. In window select your keyboard (start type name in English), then select keyboard name and Click Add
8. Click on 'Restart Now' bar will appear as in screen-shot


9. click on "Log Out" Button to logout
10. On gdm screen just click on user name "Live System User"
11. It will ask you to update folder name to your language, try your choice.

And start testing your language...

Nice to test[edit]

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

Test Results[edit]

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

How to file bugs[edit]

The following links helps you to guide to file both l10n and i18n related bugs:-

Fill one bug report by component and issue
You should fill only one bug report by component and by issue.Be sure to link the report here quickly then, to let people re-use it.

Translation teams are free to prioritize packages they find more important to test. We have made introduced a new test matrix from Fedora 18 l10n testing. Feel free to provide feedback/comments/suggestions to fltg mailing list.

  • The applications have been divided into Frequently Used Applications (FUAs) and non Frequently Used Applications (non-FUAs) for translation teams to prioritize packages for testing.
  • Further, both FUA and non-FUA lists are subdivided into project wise sections into Fedora applications, Gnome applications and Firefox.
  • The test matrix table below takes you to individual pages application-wise for testing.
  • Each test page contains test cases for each application where you can provide the test results for that application in a table format like earlier.
  • Click on the link in the second column in the below test matrix, which directs you to the test result page where you can enter your language name, code (fail/pass), bug filed and comments, if any.

Test Matrix[edit]

Components are classified project wise
Both FUA and non-FUA will have Fedora and Gnome sections

NOTE:- If you find any strings in English, kindly confirm whether its 100% translated in upstream. Link for upstream is provided along with each packages. Accordingly please file your bugs, as in some cases latest translations might not be imported.

FUAs Application List[edit]

FEDORA Applications[edit]

Package Provide Results L10n Resource Comments
example Link to test page This is a result example.
abrt QA-L10N:abrt transifex
anaconda QA-L10N:anaconda transifex You need to install live iso
authconfig QA-L10N:authconfig transifex
chkconfig QA-L10N:chkconfig transifex
cracklib QA-L10N:cracklib transifex
firewalld QA-L10N:firewalld transifex
iok QA-L10N:iok Zanata
passwd QA-L10N:passwd transifex
policycoreutils QA-L10N:policycoreutils transifex
pulseaudio QA-L10N:pulseaudio transifex
setroubleshoot QA-L10N:setroubleshoot transifex
setuptool QA-L10N:setuptool transifex
system-config-date QA-L10N:system-config-date transifex
system-config-language QA-L10N:system-config-language Zanata
system-config-printer QA-L10N:system-config-printer transifex
system-config-services QA-L10N:system-config-services transifex RHBZ #1007121, THIS IS CURRENTLY NOT READY TO TEST
system-config-users QA-L10N:system-config-users transifex
virt-manager QA-L10N:virt-manager transifex

GNOME Applications[edit]

Package Provide Results L10n Resource Comments
gnome-initial-setup QA-L10N:gnome-intial-setup transifex You need to install live iso
gdm QA-L10N:gdm gdm
gnome-clocks QA-L10N:gnome-clocks gnome-clocks
gnome-shell QA-L10N:gnome-shell gnome-shell
control-center QA-L10N:gnome-control-center gnome-control-center
empathy QA-L10N:empathy empathy
nautilus QA-L10N:nautilus nautilus
shotwell QA-L10N:shotwell shotwell
rhythmbox QA-L10N:rhythmbox rhythmbox
Evolution QA-L10N:evolution evolution
gedit QA-L10N:gedit gedit
gnome-packagekit QA-L10N:gnome-packagekit gnome-packagekit
gnome-photos QA-L10N:gnome-photos gnome-photos
bijiben QA-L10N:bijiben bijiben
gnome-weather QA-L10N:gnome-weather gnome-weather
gnome-abrt QA-L10N:gnome-abrt gnome-abrt

FIREFOX[edit]

Package Provide Results L10n Resource Comments
firefox QA-L10N:firefox firefox teams

Non-FUAs Application List[edit]