From Fedora Project Wiki
No edit summary |
Carlwgeorge (talk | contribs) m (update categories) |
||
| (86 intermediate revisions by 6 users not shown) | |||
| Line 4: | Line 4: | ||
== Objective == | == Objective == | ||
Fedora Language Testing Group [FLTG] is a [ | Fedora Language Testing Group [FLTG] is a [[SIGs|SIG]] group of Fedora contributors taking care of language testing in Fedora. | ||
Our mission is to test and review language support in Fedora and act as a bridge between translation team, i18n team and users to aid in testing languages in Fedora. | Our mission is to test and review language support in Fedora and act as a bridge between translation team, i18n team and users to aid in testing languages in Fedora. | ||
| Line 11: | Line 11: | ||
* Test the new fedora releases for our respective languages using different test cases we have prepared. | * Test the new fedora releases for our respective languages using different test cases we have prepared. | ||
* File the bugs and provide reference for other | * File the bugs and provide reference for other translators/testers. | ||
* Add new test cases based on new bugs filed and new packages. | * Add new test cases based on new bugs filed and new packages. | ||
* Prepare the ISO for testing in consultation with the release-engineering team. | * Prepare the ISO for testing in consultation with the release-engineering team. | ||
| Line 18: | Line 18: | ||
* Keep informed the l10n team about new issues, helping them to improve the testing. | * Keep informed the l10n team about new issues, helping them to improve the testing. | ||
* Submit the report on test days and collect feedback from testers. | * Submit the report on test days and collect feedback from testers. | ||
== Types of Test Days == | |||
[[L10N_QA_Test_Day|Fedora L10N Test Day]] | |||
== Why FLTG? == | |||
* To improve the quality of Fedora in our native languages. | |||
* To develop more test cases for easy and planned testing. | |||
* To help the translators/testers find the common bugs. | |||
* To have a collective testing platform where all translators can be together and test to improve their product with less bugs and errors. | |||
* A point of contact for all testers to get more information on testing events, test cases and common bugs. | |||
== Joining FLTG == | == Joining FLTG == | ||
| Line 23: | Line 35: | ||
=== IRC Channel === | === IRC Channel === | ||
<code>{{fpchat|#fedora- | <code>{{fpchat|#fedora-g11n}}</code> on Freenode | ||
Test days : #fedora-test-day on Freenode | |||
=== Mailing Lists === | === Mailing Lists === | ||
* | * [https://lists.fedoraproject.org/mailman/listinfo/g11n g11n] list - Discussions about Language Testing activities, bugs filed, test cases, feedback on testing | ||
* Earlier mail discussions are available at [http://lists.fedoraproject.org/pipermail/fltg/ FLTG Archives] | |||
=== Meetings === | === Meetings === | ||
Meetings are held weekly on ''' | Meetings are held bi-weekly on '''Wednesdays 04:30:00 UTC'''. | ||
== Tasks == | == Tasks == | ||
| Line 39: | Line 53: | ||
=== Fedora Language Test Days === | === Fedora Language Test Days === | ||
==== Fedora 18 ==== | ==== Fedora 24 ==== | ||
* [[Test_Day:2016-03-29_Translation_Test_Day|L10n Desktop Test Day (2016-03-29)]] | |||
==== Fedora 23 ==== | |||
'''Current status''': | |||
* [[Test_Day:2015-08-18_L10N|L10n Desktop Test Day (2015-08-18)]] Completed | |||
* [[Test_Day:2015-08-18_L10N#Results|Test Results]] | |||
* [[Test_Day:2015-08-18_L10N#Fedora_23_Test_Day_Report|Test Report]] | |||
* [https://fedorahosted.org/fedora-qa/ticket/473 Ticket Details] | |||
==== Fedora 22 ==== | |||
* [[FLTG/Test_Day:2015-03-17_Translation_%28l10n%29|L10n Desktop Test Day (2015-03-17)]] | |||
==== Fedora 20 ==== | |||
* [[Test_Day:2013-10-03_Translation_%28l10n%29|L10n Desktop Test Day (2013-10-03)]] Completed | |||
* [[Test_Day:2013-10-29_i18n|i18n Test Day (2013-10-29)]] Completed | |||
[https://fedorahosted.org/fedora-qa/ticket/409 Ticket - i18n testing date] | |||
[https://fedorahosted.org/fedora-qa/ticket/408 Ticket - l10n testing date] | |||
[https://fedorahosted.org/rel-eng/ticket/5781 ISO Request Ticket] | |||
'''Other important links:-''' | |||
* [https://lists.fedoraproject.org/pipermail/rel-eng/2013-September/016644.html Mail to rel-eng team] | |||
* [https://lists.fedoraproject.org/pipermail/devel-announce/2013-September/001249.html Mail to developers] | |||
* [[QA/Fedora_20_test_days|F20 QA schedule]] | |||
* [http://fedorapeople.org/groups/schedule/f-20/f-20-releng-tasks.html Fedora 20 Releng Team Tasks] | |||
==== Previous Test Days==== | |||
'''Fedora 19 **''' | |||
* [[Test_Day:2013-04-11_Translation_%28l10n%29|L10n Desktop Test Day (2013-04-11)]] Completed | |||
* [[Test_Day:2013-05-02_Localization_%28i18n%29|i18n Test Day (2013-05-02)]] Completed | |||
[[QA/Fedora_19_test_days|Fedora i18n Test Days]] | |||
[https://fedorahosted.org/fedora-qa/ticket/344 Ticket - i18n testing date] | |||
[https://fedorahosted.org/fedora-qa/ticket/345 Ticket - l10n testing date] | |||
[[FLTG/Reports/Fedora19_Test_Day_Reports#Fedora19__Test_Day_Report|Test Day Reports]] | |||
[ | [[FLTG_Feedback#Suggestion_and_feedbacks_on_Fedora_19_testing|Feedbacks Collected]] | ||
'''Fedora 18 **''' | |||
* [[Test_Day:2012-09-18_i18n|i18n Test Day (2012-09-18)]] Completed | |||
* [[Test_Day:2012-09-28_l10n|L10n Desktop Test Day (2012-09-28)]] Completed | |||
* ''L10n/i18n Installation Test Day - Due to issues with anaconda, no installation test day was conducted for F18''. | |||
[[QA/Fedora_18_test_days|Fedora i18n Test Days]] | |||
[https://fedorahosted.org/fedora-qa/ticket/301 Ticket to follow] | [https://fedorahosted.org/fedora-qa/ticket/301 Ticket to follow] | ||
[[FLTG/Reports/Test_Day_Reports#Fedora_18_Test_Day_Report|Test Day Reports]] | |||
[[FLTG_Feedback#Suggestion_and_feedbacks_on_Fedora_18_testing|Feedbacks Collected]] | |||
'''Fedora 17 **''' | |||
* [[Test_Day:2012-03-07|L10n Desktop Test Day (2012-03-07)]] Completed | |||
* [[Test_Day:2012-03-14|i18n Test Day (2012-03-14)]] Completed | |||
* [[Test_Day:2012-04-05_L10n_I18n_Installation|L10n/i18n Installation Test Day 2012-04-05]] Completed | |||
[[QA/Fedora_17_test_days|Fedora 17 Test Days]] | |||
[http://fedorahosted.org/fedora-qa/ticket/271 Ticket discussion] | |||
[[FLTG_Feedback#Suggestion_and_feedbacks_on_Fedora_17_testing|Feedbacks Collected]] | |||
* | '''**''' '''Note:''' ''FLTG started testing from Fedora 17 release.'' | ||
'''Fedora 16''' | |||
* [[Test_Day:2011-08-30_L10n_Desktop|L10n Desktop Test Day (2011-08-30)]] Completed | |||
* | * [[Test_Day:2011-08-31_L10n_I18n_Installation|L10n/i18n Installation Test Day (2011-08-31)]] Completed | ||
* [[Test_Day:2011-09-01_I18n_Desktop|i18n Test Day (2011-09-01)]] Completed | |||
[[QA/Fedora_16_test_days|Test Days]] | |||
[http://fedorahosted.org/fedora-qa/ticket/222 Ticket discussion] | |||
'''Fedora 15''' | |||
* [[Test_Day:2011-03-01_L10n_i18n_Installation|L10n/i18n installation Test Day]] | |||
* | * [[Test_Day:2011-03-03_I18n_Desktop|i18n Test Day (2011-03-03)]] Completed | ||
* [[Test_Day:2011-03-08_L10n_Desktop|L10n Test Day (2011-03-08)]] Completed | |||
'''Fedora 12''' | |||
* | * [[Test_Day:2009-10-29|i18n Test Day]] | ||
** [https:// | == Bug Reporting == | ||
Filing a bug is the most important task in testing as reporting the problems you encounter help developers to fix the issue and make the product for best use. Each project has its own way to file bugs and bug reporting process for Fedora and Gnome is explained below. | |||
=== Instructions to file bugs in Fedora === | |||
* To file l10n bugs in Fedora, please visit [[L10N#Bug_Reporting.2C_Testing.2C_and_Quality_Assurance|here]]. | |||
* To file i18n bugs in Fedora, please visit [[I18N/Bugs/Guidelines|here]]. | |||
=== Instructions to file bugs in Gnome === | |||
Bugs pertaining to Gnome must be filed in [https://bugzilla.gnome.org/ Gnome Bugzilla]. To file l10n bugs in Gnome, please follow the instructions mentioned [[FLTG/Gnome_bug_filing_instructions|here]]. | |||
=== Language Bug Triage === | === Language Bug Triage === | ||
| Line 88: | Line 191: | ||
List need to create in Bugzilla 'TODO' | List need to create in Bugzilla 'TODO' | ||
== Fedora 18 | == New i18n Features to be included for testing == | ||
=== Fedora 18 === | |||
- [https://fedoraproject.org/wiki/Features/Fontconfig2.10 Fontconfig 2.0] | - [https://fedoraproject.org/wiki/Features/Fontconfig2.10 Fontconfig 2.0] | ||
- [ | - [[Features/GNOMEIBusIntegration|Gnome Ibus Integration]] | ||
- [ | - [[Features/ibus-libpinyin|ibus-libpinyin]] | ||
- [ | - [[Features/Typing-Booster|Typing Booster]] | ||
- [ | - [[Features/InitialExperience|Gnome Initial Experience]] | ||
- [ | - [[Features/Liberation_Fonts_2|Liberation Fonts 2]] | ||
- [https://fedoraproject.org/wiki/Features/NewInstallerUI New Installer (anaconda)] | - [https://fedoraproject.org/wiki/Features/NewInstallerUI New Installer (anaconda)] | ||
== Fedora 17 | === Fedora 17 === | ||
- [ | - [[Features/IndicUnicode6|Indian Language Unicode 6]] | ||
- [ | - [[Features/GnomeInputIntegration|Gnome Input Integration ibus]] | ||
- [ | - [[Features/libpinyin|libpinyin]] | ||
- [ | - [[Features/Inscript2_Keymaps|Inscript2]] | ||
- [ | - [[Features/FontConfigurationTool|Font Configuration Tool]] | ||
- [https://fedorahosted.org/eekboard/ Eekboard] | - [https://fedorahosted.org/eekboard/ Eekboard] | ||
== Reports == | |||
Reports give you all the details like languages participated in testing, number of applications tested, no of bugs filed etc. Reports for l10n and i18n test days are available below : | |||
[[FLTG/Reports/Fedora19_Test_Day_Reports#Fedora_19_Test_Day_Report|Fedora 19]] | |||
[[FLTG/Reports/Test_Day_Reports#Fedora_18_Test_Day_Report|Fedora 18]] | |||
== Feedback == | |||
After every test event FLTG makes sure that all feedback and suggestions are collected from the community. This helps us to improve our future testing events and make things easy for our testers. All feedbacks from community are recorded [[FLTG/Feedback|here]]. | |||
== Check-list for FLTG Members == | |||
This list explains the step-by-step tasks executed by the FLTG group before every testing event. Each members choose their tasks and work collectively towards making the testing event successful. To view the list click [[FLTG/CHECK_LIST|here]]. | |||
== Members == | == Members == | ||
| Line 136: | Line 257: | ||
* [[User:pravins| Pravin Satpute]] (pravins) | * [[User:pravins| Pravin Satpute]] (pravins) | ||
* [[User:Smaitra| Satyabrata Maitra]] (Satya) | |||
[[Category:SIGs]] | |||
[[Category:Fedora special-interest groups]] | |||
Latest revision as of 03:46, 27 December 2018
Objective
Fedora Language Testing Group [FLTG] is a SIG group of Fedora contributors taking care of language testing in Fedora.
Our mission is to test and review language support in Fedora and act as a bridge between translation team, i18n team and users to aid in testing languages in Fedora.
What do we do
- Test the new fedora releases for our respective languages using different test cases we have prepared.
- File the bugs and provide reference for other translators/testers.
- Add new test cases based on new bugs filed and new packages.
- Prepare the ISO for testing in consultation with the release-engineering team.
- Coordinate and conduct both i18n (with the help of Fedora i18n team) and 110n test days.
- Based on the ISO selected for testing, review the test cases.
- Keep informed the l10n team about new issues, helping them to improve the testing.
- Submit the report on test days and collect feedback from testers.
Types of Test Days
Why FLTG?
- To improve the quality of Fedora in our native languages.
- To develop more test cases for easy and planned testing.
- To help the translators/testers find the common bugs.
- To have a collective testing platform where all translators can be together and test to improve their product with less bugs and errors.
- A point of contact for all testers to get more information on testing events, test cases and common bugs.
Joining FLTG
IRC Channel
#fedora-g11n[?] on Freenode
Test days : #fedora-test-day on Freenode
Mailing Lists
- g11n list - Discussions about Language Testing activities, bugs filed, test cases, feedback on testing
- Earlier mail discussions are available at FLTG Archives
Meetings
Meetings are held bi-weekly on Wednesdays 04:30:00 UTC.
Tasks
Fedora Language Test Days
Fedora 24
Fedora 23
Current status:
- L10n Desktop Test Day (2015-08-18) Completed
Fedora 22
Fedora 20
- L10n Desktop Test Day (2013-10-03) Completed
- i18n Test Day (2013-10-29) Completed
Other important links:-
Previous Test Days
Fedora 19 **
- L10n Desktop Test Day (2013-04-11) Completed
- i18n Test Day (2013-05-02) Completed
Fedora 18 **
- i18n Test Day (2012-09-18) Completed
- L10n Desktop Test Day (2012-09-28) Completed
- L10n/i18n Installation Test Day - Due to issues with anaconda, no installation test day was conducted for F18.
Fedora 17 **
- L10n Desktop Test Day (2012-03-07) Completed
- i18n Test Day (2012-03-14) Completed
** Note: FLTG started testing from Fedora 17 release.
Fedora 16
- L10n Desktop Test Day (2011-08-30) Completed
- i18n Test Day (2011-09-01) Completed
Fedora 15
- i18n Test Day (2011-03-03) Completed
- L10n Test Day (2011-03-08) Completed
Fedora 12
Bug Reporting
Filing a bug is the most important task in testing as reporting the problems you encounter help developers to fix the issue and make the product for best use. Each project has its own way to file bugs and bug reporting process for Fedora and Gnome is explained below.
Instructions to file bugs in Fedora
Instructions to file bugs in Gnome
Bugs pertaining to Gnome must be filed in Gnome Bugzilla. To file l10n bugs in Gnome, please follow the instructions mentioned here.
Language Bug Triage
List need to create in Bugzilla 'TODO'
New i18n Features to be included for testing
Fedora 18
Fedora 17
- Gnome Input Integration ibus
- Eekboard
Reports
Reports give you all the details like languages participated in testing, number of applications tested, no of bugs filed etc. Reports for l10n and i18n test days are available below :
Feedback
After every test event FLTG makes sure that all feedback and suggestions are collected from the community. This helps us to improve our future testing events and make things easy for our testers. All feedbacks from community are recorded here.
Check-list for FLTG Members
This list explains the step-by-step tasks executed by the FLTG group before every testing event. Each members choose their tasks and work collectively towards making the testing event successful. To view the list click here.
Members
- A S Alam (asa)
- Jaswinder Singh (jassy)
- Ani Peter (apeter)
- Sweta Kothari (swkothar)
- Kévin Raymond (shaiton)
- Nilamdyuti Goswami (ngoswami)
- Manoj Kumar Giri (mgiri)
- Pravin Satpute (pravins)
- Satyabrata Maitra (Satya)