From Fedora Project Wiki

No edit summary
Line 9: Line 9:
| fedora_mailing_list = test
| fedora_mailing_list = test
}}
}}
{{admon/warning|Page under construction|This page and the information contained aren't complete. Please come back when the time of this Test Day will come.}}


{{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.}}
{{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.}}
Line 16: Line 14:
== What to test? ==
== What to test? ==


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


== Who's available ==
== Who's available ==


The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
* Development - [[user:Pravins|Pravin Satpute]] (pravins) [[user:Aalam|Aman Alam]] (aalam) [[User:Pnemade|Parag Nemade]] (paragan)
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
* Quality Assurance - [[user:Anipeter|Ani Peter]] (apeter) [[user:Smaitra|Satyabrata Maitra]] (Satya)
* Localization - [[user:Noriko|Noriko Mizumoto]] (noriko)


== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  


List any prerequisite needs for the test event. A fresh system, virtualized guest, a blank DVD ... a desire to break software?
* Bare metal or virtual machine. [https://fedoraproject.org/wiki/Getting_started_with_virtualization Start with Virtualization]
* Usb key, a virtualized guest or a burned CD/DVD with the test image.


* Usb key
== How to test? ==
* Usb externally connected HD IDE/SATA
* Empty HD IDE/SATA/SCSI
* Free space on HD


Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
=== Prepare Your System ===


* An updated [http://fedoraproject.org/get-prerelease Fedora XX pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
* Tests requiring ''physical media'' (e.g. DVD or CD images)
* You may download a non-destructive Fedora 24 live image for your architecture. The specific live image for L10N tests can be found here. Tips on using a live image are available at [[FedoraLiveCD]]
* Unless otherwise noted, you may use nightly Fedora 24 ''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.


== How to test? ==
=== How to run desktop in your language? ===


High level details on how a contributor can get involved. This can include (but not limited to):
{{Admon/tip | LOGGING OFF DOES NOT WORK ON LIVECD | The normal steps to setup desktop in your language will not work for this live image for F24 test day.}}


* Areas to target with exploratory testing
* A list of pre-defined test cases to execute
* How to report back results


Here's another common chunk (again, replace XX as above):
To check translations in your own language, after booting from '''Live''' iso kindly do the following:  <br />
* Open gnome-terminal and run command " locale.LANGUAGE=<your language code> ", eg: locale.LANGUAGE=cs_CZ.
* Run the desired applications from console.
* Check translations.


=== '''Update your machine''' ===
== The Testing Process ==


If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
=== Testdayapp ===


=== '''Live image''' ===
* The testdayapp is a new interface developed by Josef Skladanka for Fedora test events. From Fedora 23 L10n test day, we have been using this app to test the l10n packages and provide the test results.
* Testdayapp for Fedora 23 L10n Testing is [http://209.132.184.193/testdays/show_event?event_id=28 here].


Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
===Steps for testers ===


== Test Cases ==
* Translation teams/translators are free to prioritize packages they find more important to test.
* Go to the [http://209.132.184.193/testdays/show_event?event_id=28 Fedora 23 app] page.
* Applications to test is categorised into Fedora, Gnome and Firefox. For better viewing and to avoid cluttering, these applications are further divided into 4-5 sections.
* Click on the application name you would like to test. This will take you to the testcase page of that application explaining you about the application and steps to test.
* After completing the testing process of each application, press on the "Enter Result" shown below each applications. This will take you to a form where you can enter the test results for that particular application. Please enter the enter in the form as shown below and click on "Submit" :
    * Username = Your name OR FAS name
    * Hardware name = Lang code
    * Select the result as PASSED or FAILED or INFO
    * Bugs = Bug number of the filed bug.
    * Mention your comments or notes in the COMMENT section
* Continue testing of all applications and provide the test results as mentioned above.


Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].


== Test Results ==
== 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:
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.
 
== How to file 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]
* [https://fedoraproject.org/wiki/I18N/Bugs/Guidelines Instructions to file i18n bugs]
* [https://fedoraproject.org/wiki/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.}}
 
== List of applications and place for l10n ==
 
 
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].
 
'''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.
 
 
=== FEDORA Applications ===
 
{| class="wikitable sortable" style="width: 50%" rowbgcolor="#3074c2" rowstyle="color: white; font-weight: bold;" 55%
! Package !! L10n Resource
|-
| {{package|abrt}} || [https://fedora.zanata.org/project/view/abrt Zanata]
|-
| {{package|anaconda}}  || [https://fedora.zanata.org/project/view/anaconda Zanata]
|-
| {{package|authconfig}} || [https://fedora.zanata.org/project/view/authconfig Zanata]
|-
| {{package|blivet-gui}} || [https://fedora.zanata.org/project/view/blivet/ Zanata]
|-
| {{package|chkconfig}} || [https://fedora.zanata.org/project/view/chkconfig/versions Zanata]
|-
| {{package|comps}} || [https://fedora.zanata.org/project/view/comps Zanata]
|-
| {{package|dnf}} || [https://fedora.zanata.org/project/view/dnf Zanata]
|-
| {{package|firewalld}} || [https://fedora.zanata.org/project/view/firewalld Zanata]
|-
| {{package|iok}} || [https://fedora.zanata.org/project/view/iok Zanata]
|-
| {{package|libpwquality}} || [https://fedora.zanata.org/project/view/libpwquality/ Zanata]
|-
| {{package|passwd}} || [https://fedora.zanata.org/project/view/passwd/ Zanata]
|-
| {{package|policycoreutils}} || [https://fedora.zanata.org/project/view/selinux Zanata]
|-
| {{package|setroubleshoot}} || [https://fedora.zanata.org/project/view/setroubleshoot Zanata]
|-
| {{package|system-config-firewall}} || [https://fedora.zanata.org/project/view/system-config-firewall Zanata]
|-
| {{package|system-config-language}} || [https://translate.zanata.org/zanata/project/view/system-config-language Zanata]
|-
| {{package|system-config-printer}} || [https://fedora.zanata.org/project/view/system-config-printer Zanata]
|-
| {{package|virt-manager}} || [https://fedora.zanata.org/project/view/virt-manager/ Zanata]
|-
| {{package|virt-viewer}} || [https://fedora.zanata.org/project/view/virt-viewer Zanata]
|-
|}


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. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
=== GNOME Applications ===


{|
{| class="wikitable sortable" style="width: 50%" rowbgcolor="#3074c2" rowstyle="color: white; font-weight: bold;" 55%
! User
! Package !!L10n Resource
! [[QA:Testcase_sample_1|Sample test 1]]
|-
! [[QA:Testcase_sample_2|Sample test 2]]
| {{package|gdm}} || [http://l10n.gnome.org/module/gdm/ gdm]
! [[QA:Testcase_sample_3|Sample test 3]]
|-
! [[QA:Testcase_sample_4|Sample test 4]]
| {{package|gnome-boxes}} || [http://l10n.gnome.org/module/gnome-boxes/ gnome-boxes]
! References
|-
| {{package|gnome-clocks}} || [http://l10n.gnome.org/module/gnome-clocks/ gnome-clocks]
|-
| {{package|gnome-font-viewer}} || [http://l10n.gnome.org/module/gnome-font-viewer/ gnome-font-viewer]
|-
| {{package|gnome-keyring}} || [http://l10n.gnome.org/module/gnome-keyring/ gnome-keyring]
|-
| {{package|gnome-online-accounts}} || [http://l10n.gnome.org/module/gnome-online-accounts/ gnome-online-accounts]
|-
| {{package|gnome-screenshot}} || [http://l10n.gnome.org/module/gnome-screenshot/ gnome-screenshot]
|-
| {{package|gnome-shell}} || [http://l10n.gnome.org/module/gnome-shell/ gnome-shell]
|-
| {{package|gnome-system-monitor}} || [http://l10n.gnome.org/module/gnome-system-monitor/ gnome-system-monitor]
|-
| {{package|gnome-terminal}} || [http://l10n.gnome.org/module/gnome-terminal/ gnome-terminal]
|-
| {{package|control-center}} || [http://l10n.gnome.org/module/gnome-control-center/ gnome-control-center]
|-
| {{package|empathy}} || [http://l10n.gnome.org/module/empathy/ empathy]
|-
| {{package|nautilus}} || [http://l10n.gnome.org/module/nautilus/ nautilus]
|-
| {{package|NetworkManager}} || [http://l10n.gnome.org/module/NetworkManager/ NetworkManager]
|-
| {{package|shotwell}} || [https://www.transifex.com/projects/p/shotwell/ shotwell]
|-
| {{package|rhythmbox}} || [http://l10n.gnome.org/module/rhythmbox/ rhythmbox]
|-
| {{package|Evolution}} || [https://l10n.gnome.org/module/evolution/ evolution]
|-
| {{package|gedit}} || [https://l10n.gnome.org/module/gedit/ gedit]
|-
| {{package|gnome-packagekit}} || [https://l10n.gnome.org/module/gnome-packagekit/ gnome-packagekit]
|-
|-
| [[User:SampleUser|Sample User]]
| {{package|gnome-photos}} || [https://l10n.gnome.org/module/gnome-photos/ gnome-photos]
| {{result|none}}  
|-
| {{result|pass}}
| {{package|bijiben }} || [https://l10n.gnome.org/module/bijiben/ bijiben]
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
|-
| {{result|fail}} <ref>{{bz|12345}}</ref>
| {{package|gnome-weather }} || [https://l10n.gnome.org/module/gnome-weather/ gnome-weather]
| <references/>
|-
| {{package|gnome-abrt}} || [https://l10n.gnome.org/module/gnome-abrt/ gnome-abrt]
|-
|-
|}
|}


[[Category:Fedora 24 Test Days]]
=== FIREFOX ===
 
{| class="wikitable sortable" style="width: 50%" rowbgcolor="#3074c2" rowstyle="color: white; font-weight: bold;" 55%
! Package !!L10n Resource
|-
| {{package|firefox}} || [http://l10n.mozilla.org/teams/ firefox teams]
|-}
|}
 
 
[[Category:Fedora 23 Test Days]]

Revision as of 12:08, 28 March 2016

Fedora Test Days
Translation
Date 2016-03-29
Time all day
Website QA/Fedora_24_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 translations availability and accuracy 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

  • Bare metal or virtual machine. Start with Virtualization
  • 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)
  • You may download a non-destructive Fedora 24 live image for your architecture. The specific live image for L10N tests can be found here. Tips on using a live image are available at FedoraLiveCD
  • Unless otherwise noted, you may use nightly Fedora 24 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?

LOGGING OFF DOES NOT WORK ON LIVECD
The normal steps to setup desktop in your language will not work for this live image for F24 test day.


To check translations in your own language, after booting from Live iso kindly do the following:

  • Open gnome-terminal and run command " locale.LANGUAGE=<your language code> ", eg: locale.LANGUAGE=cs_CZ.
  • Run the desired applications from console.
  • Check translations.

The Testing Process

Testdayapp

  • The testdayapp is a new interface developed by Josef Skladanka for Fedora test events. From Fedora 23 L10n test day, we have been using this app to test the l10n packages and provide the test results.
  • Testdayapp for Fedora 23 L10n Testing is here.

Steps for testers

  • Translation teams/translators are free to prioritize packages they find more important to test.
  • Go to the Fedora 23 app page.
  • Applications to test is categorised into Fedora, Gnome and Firefox. For better viewing and to avoid cluttering, these applications are further divided into 4-5 sections.
  • Click on the application name you would like to test. This will take you to the testcase page of that application explaining you about the application and steps to test.
  • After completing the testing process of each application, press on the "Enter Result" shown below each applications. This will take you to a form where you can enter the test results for that particular application. Please enter the enter in the form as shown below and click on "Submit" :
   * Username = Your name OR FAS name
   * Hardware name = Lang code
   * Select the result as PASSED or FAILED or INFO
   * Bugs = Bug number of the filed bug.
   * Mention your comments or notes in the COMMENT section
  • Continue testing of all applications and provide the test results as mentioned above.


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

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.

List of applications and place for l10n

Gnome bugs can be reported as per instructions provided 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.


FEDORA Applications

Package L10n Resource
abrt Zanata
anaconda Zanata
authconfig Zanata
blivet-gui Zanata
chkconfig Zanata
comps Zanata
dnf Zanata
firewalld Zanata
iok Zanata
libpwquality Zanata
passwd Zanata
policycoreutils Zanata
setroubleshoot Zanata
system-config-firewall Zanata
system-config-language Zanata
system-config-printer Zanata
virt-manager Zanata
virt-viewer Zanata

GNOME Applications

Package L10n Resource
gdm gdm
gnome-boxes gnome-boxes
gnome-clocks gnome-clocks
gnome-font-viewer gnome-font-viewer
gnome-keyring gnome-keyring
gnome-online-accounts gnome-online-accounts
gnome-screenshot gnome-screenshot
gnome-shell gnome-shell
gnome-system-monitor gnome-system-monitor
gnome-terminal gnome-terminal
control-center gnome-control-center
empathy empathy
nautilus nautilus
NetworkManager NetworkManager
shotwell shotwell
rhythmbox rhythmbox
Evolution evolution
gedit gedit
gnome-packagekit gnome-packagekit
gnome-photos gnome-photos
bijiben bijiben
gnome-weather gnome-weather
gnome-abrt gnome-abrt

FIREFOX

Package L10n Resource
firefox firefox teams
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2016-03-29_Translation_Test_Day&oldid=441073"