From Fedora Project Wiki

Revision as of 02:48, 12 February 2011 by Igor (talk | contribs) (Create page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Warning.png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
DATE TIME WHERE
2011-03-08 All Day #fedora-test-day (webirc)
Note.png
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 - which should be linked at QA/Test_Days - 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.
  • 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) -- [Link_to_alpha download F-15-Alpha].
  • Unless otherwise noted, you may use nightly Fedora 15 branch install images. Review for information on downloading and installing Branched.
  • Optionally, you may download a non-destructive Fedora 15 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.

Test Cases

Fedora 15 l10n Results Template

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.

Translation teams are free to prioritize and post tests in the way they find better suitable for their needs. Teams can post links for their test results here:

User Language Link to results
Sample User Sample language Test results