|Fedora Test Days|
What to test?
Today's installment of Fedora Test Day will focus on translations availability and accuracy in desktop applications
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Pravin Satpute (pravins) Aman Alam (aalam) Parag Nemade (paragan)
- Quality Assurance - Ani Peter (apeter) Satyabrata Maitra (Satya)
- Localization - Noriko Mizumoto (noriko)
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. x86_64 can be downloaded from 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?
To check translations in your own language, after booting from Live iso kindly do the following:
- Open gnome-terminal and run command
export LANGUAGE=<your language code>
- Run the desired applications from console.
- Check translations.
The Testing Process
- The testdayapp is a new interface developed by Josef Skladanka for Fedora test events. From Fedora 23 L10n testing, we have been using this web interface to test the l10n packages and provide the test results.
- Testdayapp for Fedora 24 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 24 app page.
- Applications to test is categorized 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 * Profile = Your Profile link * Result = Select the result from the drop down menu 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.
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:-
- Instructions to file l10n bugs => F24 new bug template
- Instructions to file i18n bugs
- Instructions to file GNOME bugs
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.