L10N and I18N Installation Test Day Tomorrow
by Ani Peter
Hello everyone!
Please note that tomorrow (2012-04-05) we are hosting a Localization and
Internationalization Installation Test Day [1] to have a look on the
translations quality for Anaconda and i18n support during installation
as well as some post install verification tests.
Kindly request all Fedora translators to participate in this test event.
Please check [1] for details and also feel free to edit the wiki with
your results.
Thanking you
Best regards
Ani
[1] -
https://fedoraproject.org/wiki/Test_Day:2012-04-05_L10n_I18n_Installation
11 years, 4 months
#5306: Live Image for F18 i18n and L10n QA Test
by Fedora Release Engineering
#5306: Live Image for F18 i18n and L10n QA Test
-----------------------------+------------------------
Reporter: jassy | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 18 Alpha | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Please compose Live image of Software Review UI for i18n and Translation:
Current i18n Test Day: 2012-09-04
Current Translation Test day: 2012-09-06
so better if we have image ready few day before actual test day
(2012-09-04).
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5306>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
11 years, 6 months
l10n qa test feedback
by Noriko Mizumoto
Hi fltg team
Here is some feedback:
[anaconda test]
Test matrix says 'this testing is optional as anaconda is not stable
enough for installation testing'. But actually anaconda did work
somewhat thus I was able to install f18 (it was unpleasant experience
though). I am afraid of that this warning can cause testers to walk away
from filling any result. I think, regardless it is stable or unstable, a
test should be performed and the result to be entered. So that a bug is
filed, giving another pressure to the developer to fix. No bug is taken
as 'good' from l10n side. How you think?
[comps test]
If my understanding is correct, comps is part of the installer
(anaconda) and should be tested during installation process. However,
this test entry shows up after 'chkconfig'. Once installation completes,
comps sole test can not be performed. Therefore again, no result has
been filled atm. Next time, it might be better to have anaconda and
comps in one entry, how you think?
[Others]
There are some packages not available for test and tagged as 'this is
currently not ready to test' in Comments. Other than firstboot, I am not
sure why is that. Has any bug/ticket been filed? If so, could you add
the bug/ticket number, so that tester who has interest can read?
Thanks
noriko
11 years, 6 months
