#158: Proposed Test Day - l10n/i18n test day
-----------------------+----------------------------------------------------
Reporter: rhe | Owner: rhe
Type: task | Status: new
Priority: major | Milestone: Fedora 15
Component: Test Day | Version:
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Comment (by rhe):
Replying to [comment:4 aalam]:
Replying to [comment:3 igor]:
> I prefer to use the formatted wiki test day result page as before. I
intend to keep the l10n template just as a guide for translation teams to
know which modules need testing, but it also have to be updated.
>
> I'd like to give a special attention this time for langpack
installation. Mainly regarding langpacks for Firefox 4 and Libre Office.
And we also should target font rendering and input methods as usual.
>
Langpack is good idea to test. Libre office has separate packages, but
firefox don't have separate. Also we can test Language group support,
which is by default installed by fedora (yum groupinstall
<LANGUAGE>-support).
for Rendering and Input, we can have 4 basic test groups:
- pango - gedit/firefox
- qt - kwrite
- icu - libre office
- input - ibus
- Printing - (can be print to file only - ps/pdf/svg)
> We have two different groups of i18n test cases: installation and
desktop related ones. So I'd divide the test days into those two groups
rather than into i18n and l10n. Testers will hit both i18n and l10n bugs
while running the tests anyway, and sometimes depending of the bug will be
hard to figure out if it is a i18n or l10n bug at the moment, what can be
done by further bug triage.
installation and desktop can better idea than i18n/l10n grouping.
Actually Rendering/Input/Font Testing requires few applications (as
above), while for Basic translated Desktop we can test all default
installed application (with desktop) for a language.
> Of course we can try another approach, but since we have an
intersection between l10n and i18n I think we can use it in our favor.
Can we use hybrid (mixed) approach?
- installation - i18n/l10n (Single)
- Desktop - two separate
- l10n (Translation of default installed application)
- i18n (input/rendering/printing) with one (or two) from each
rendering engine.
Installation tests can be hosted in one day, I've added
Tuesday(2011-03-01) as installation test day like Adam suggested. How
about the desktop part? If all of these are included, do you think one day
is enough for desktop?
--
Ticket URL: <
https://fedorahosted.org/fedora-qa/ticket/158#comment:6>
Fedora QA <
http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance