No edit summary |
No edit summary |
||
| 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 == | |||
[[https://fedoraproject.org/wiki/L10N_QA_Test_Day Fedora L10N Test Day]] | |||
== Why FLTG? == | == Why FLTG? == | ||
Revision as of 07:08, 27 June 2014
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-fltg[?] on Freenode
Mailing Lists
- fltg list - Discussions about Language Testing activities, bugs filed, test cases, feedback on testing
- Mail discussions are available at FLTG Archives
Meetings
Meetings are held weekly on Tuesdays, 0930 UTC.
Tasks
Fedora Language Test Days
Fedora 20
Current status:
- 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)