I sent an email to the L10N list announcing the test day and requesting feedback from translators and team coordinators: http://lists.fedoraproject.org/pipermail/trans/2010-July/007857.html

Based on their feedback we can change the existing test cases in order to make them more suitable for the test day.

It would be kind for translators if each test case page contains 'where and how to report if failed' information.
[[BR]]

If good number of translators have interest to join, this event would be better included in the trans-task schedule so that the reminder by John to be sent automatically on time.

Replying to [comment:1 igor]:

I sent an email to the L10N list announcing the test day and requesting feedback from translators and team coordinators: http://lists.fedoraproject.org/pipermail/trans/2010-July/007857.html

Based on their feedback we can change the existing test cases in order to make them more suitable for the test day.

Thanks a lot Igor, hopefully we can get some suggestion on these tests. And if you have any thoughts, feel free to improve, or discuss with them here as well. :)

Replying to [comment:2 noriko]:

It would be kind for translators if each test case page contains 'where and how to report if failed' information.
[[BR]]
You are right. But on that day, its test day page([https://fedoraproject.org/wiki/Test_Day:2010-02-25_YumLangpackPlugin example page]) will be provided with detailed instructions for testers.

If good number of translators have interest to join, this event would be better included in the trans-task schedule so that the reminder by John to be sent automatically on time.

Thanks, an announcement will also be sent out as a reminder one or two days before the test day.

I started writing a draft page for the test day:
https://fedoraproject.org/wiki/Test_Day:2010-09-09_AnacondaTranslationKeyboard

We need to discuss some details such as:
* Time - Maybe you guys can suggest an UTC time that might be good for you. Normally I'm available between 14 UTC - 19 UTC and 23 UTC - 04:00 UTC just to let you know.

• I'm not sure if a smolt profile helps in those tests. IMHO requiring them might add unnecessary complexity for users who are willing to participate since the profiles don't show the keyboard layout, only the language.

• Which test image will we use, that one specific for translators or an updated nightly build? IMHO we should use the one more updated at the time.

Hi Igor,

Sorry I didn't reply to this thread in time. I'm quite busy executing release validation tests these days. Will concentrate on this event as soon as I have time this week.

Thanks,
Hurry

Replying to [comment:5 igor]:

I started writing a draft page for the test day:
https://fedoraproject.org/wiki/Test_Day:2010-09-09_AnacondaTranslationKeyboard

We need to discuss some details such as:
* Time - Maybe you guys can suggest an UTC time that might be good for you. Normally I'm available between 14 UTC - 19 UTC and 23 UTC - 04:00 UTC just to let you know.

• I'm not sure if a smolt profile helps in those tests. IMHO requiring them might add unnecessary complexity for users who are willing to participate since the profiles don't show the keyboard layout, only the language.

• Which test image will we use, that one specific for translators or an updated nightly build? IMHO we should use the one more updated at the time.

Hi Igor,

Sorry for the delay, finally I got the time to concentrate on it. I've read [https://fedoraproject.org/wiki/Test_Day:2010-09-09_AnacondaTranslationKeyboard] and made some modification on it, please review it. The main changes include:

• The test day time changed to 'all day', since testers from different time zones will attend it.
• Besides live image, I added pre-release candidates(Supposed to be F14 Beta TC) as requirements for testing.
• The test result table changed for testers to offer results.

Replying to [comment:5 igor]:

I started writing a draft page for the test day:
https://fedoraproject.org/wiki/Test_Day:2010-09-09_AnacondaTranslationKeyboard

We need to discuss some details such as:
* Time - Maybe you guys can suggest an UTC time that might be good for you. Normally I'm available between 14 UTC - 19 UTC and 23 UTC - 04:00 UTC just to let you know.

I'm normally available from 1 UTC - 11 UTC, and members from your team and i18n team can also come for help, so let's just write down 'all day' there. :)

• I'm not sure if a smolt profile helps in those tests. IMHO requiring them might add unnecessary complexity for users who are willing to participate since the profiles don't show the keyboard layout, only the language.

Agree, so I removed it.

• Which test image will we use, that one specific for translators or an updated nightly build? IMHO we should use the one more updated at the time.

I planed to use F14 Beta Test Compose(Boot.iso CD DVD) as the main testing image, but since Alpha slipped for a week, Beta TC won't be available on 09-09 in some time zones[1]. And the nightly composed live image is not stable and can't reflect all the issues happened during install. So I don't know how to make this test day unless postponing it to 09-16, the next open slot. What do you think?

I also noticed that you put the l10n template on the page, do you also want to cover the tests on this template? Then I think there will be too many tests for a test day. But we can arrange another one for it if you want.

Thanks,
Hurry
[1] http://poelstra.fedorapeople.org/schedules/f-14/f-14-releng-tasks.html

Replying to [comment:7 rhe]:

Hi Igor,

Sorry for the delay, finally I got the time to concentrate on it. I've read [https://fedoraproject.org/wiki/Test_Day:2010-09-09_AnacondaTranslationKeyboard] and made some modification on it, please review it. The main changes include:

• The test day time changed to 'all day', since testers from different time zones will attend it.
• Besides live image, I added pre-release candidates(Supposed to be F14 Beta TC) as requirements for testing.
• The test result table changed for testers to offer results.

Thanks for making it better Hurry!

Replying to [comment:5 igor]:

I started writing a draft page for the test day:
https://fedoraproject.org/wiki/Test_Day:2010-09-09_AnacondaTranslationKeyboard

We need to discuss some details such as:
* Time - Maybe you guys can suggest an UTC time that might be good for you. Normally I'm available between 14 UTC - 19 UTC and 23 UTC - 04:00 UTC just to let you know.

I'm normally available from 1 UTC - 11 UTC, and members from your team and i18n team can also come for help, so let's just write down 'all day' there. :)

Nice, it is better to host it during the whole day so we get more contributors.

• Which test image will we use, that one specific for translators or an updated nightly build? IMHO we should use the one more updated at the time.

I planed to use F14 Beta Test Compose(Boot.iso CD DVD) as the main testing image, but since Alpha slipped for a week, Beta TC won't be available on 09-09 in some time zones[1]. And the nightly composed live image is not stable and can't reflect all the issues happened during install. So I don't know how to make this test day unless postponing it to 09-16, the next open slot. What do you think?

I'm in favor of postpone it but it seems to me that 09-16 is now occupied for the systemd test day [1]. So the the next open slot left is 10-07 which is pretty close to the Final Change Deadline. I still think it is worth postponing it if we are able to better test it that day.

I also noticed that you put the l10n template on the page, do you also want to cover the tests on this template? Then I think there will be too many tests for a test day. But we can arrange another one for it if you want.

You're right. I didn't realized that it could be too many tests. Let's stick to the keyboard tests for now, but is natural that some translation bugs will be noticed during those tests. Anyway it is a good idea to focus on our primary objective.

[1] https://fedoraproject.org/wiki/QA/Fedora_14_test_days

Regards,
Igor

Replying to [comment:8 igor]:

Replying to [comment:7 rhe]:
<skip>

I'm in favor of postpone it but it seems to me that 09-16 is now occupied for the systemd test day [1]. So the the next open slot left is 10-07 which is pretty close to the Final Change Deadline. I still think it is worth postponing it if we are able to better test it that day.

Ah, right, it was occupied yesterday.:) I've asked Adam to see if we can exchange the time[*].

[*] https://fedorahosted.org/fedora-qa/ticket/104

I also noticed that you put the l10n template on the page, do you also want to cover the tests on this template? Then I think there will be too many tests for a test day. But we can arrange another one for it if you want.

You're right. I didn't realized that it could be too many tests. Let's stick to the keyboard tests for now, but is natural that some translation bugs will be noticed during those tests. Anyway it is a good idea to focus on our primary objective.

Thanks.

Rgds,[[BR]]

Hurry

I'm in favor of postpone it but it seems to me that 09-16 is now occupied for the systemd test day [1]. So the the next open slot left is 10-07 which is pretty close to the Final Change Deadline. I still think it is worth postponing it if we are able to better test it that day.

Ah, right, it was occupied yesterday.:) I've asked Adam to see if we can exchange the time[*].

[*] https://fedorahosted.org/fedora-qa/ticket/104

Nice, it would be a lot better to host it on 09-16. So let's wait for Adam's reply.

Thanks,
Igor

Replying to [comment:10 igor]:

Nice, it would be a lot better to host it on 09-16. So let's wait for Adam's reply.

Hi Igor, good news! Adam has agreed to exchange the time, so we'll host it on 09-16. I've moved the test day page to：
* https://fedoraproject.org/wiki/Test_Day:2010-09-16_AnacondaTranslationKeyboard
and added it to the test days schedule.

I think the next step is to improve the [https://fedoraproject.org/wiki/Test_Day:2010-09-16_AnacondaTranslationKeyboard#Test_Cases test cases]. So how do you think about them? Is there anything we need to modify/correct/cover?

Great Hurry!

I will work on the test cases in the next days.

I don't think we need more test cases, just improve the ones we already have. For instance, I would like to add some post install steps, just to check if Anaconda did its job correctly during the installation. IMHO we should cover at least the installation using GNOME and KDE desktop environments and make that clear in the test cases. A few releases back some keymaps were buggy when using different toolkits. The Non-English European Language Install test case might need some changes to cover the differences between the languages as well. I will install F14 Alpha and see if there is something else we need to cover.

Replying to [comment:12 igor]:

Great Hurry!

I will work on the test cases in the next days.

I don't think we need more test cases, just improve the ones we already have. For instance, I would like to add some post install steps, just to check if Anaconda did its job correctly during the installation. IMHO we should cover at least the installation using GNOME and KDE desktop environments and make that clear in the test cases. A few releases back some keymaps were buggy when using different toolkits. The Non-English European Language Install test case might need some changes to cover the differences between the languages as well. I will install F14 Alpha and see if there is something else we need to cover.

Thank you Igor! You know about the translation/keyboards much better, so please go ahead and improve the tests as you want.

I would like to help regarding i18n/l10n test cases.
for Asian Languages, we need to add few steps, if user is using boot.iso or network install, then Stage I (anaconda) installer, Asian languages are using English text and Stage II, it starts with selected language. Keymap need to keep in English, default is English.

Hi aalam,

Sorry for the delay.

Replying to [comment:14 aalam]:

I would like to help regarding i18n/l10n test cases.

Welcome! Igor will also make some modifications on the tests, so please add your suggestion here like you did so that he can see it.

for Asian Languages, we need to add few steps, if user is using boot.iso or network install, then Stage I (anaconda) installer, Asian languages are using English text

Yeah, but I think for every language and media, before language selection step(stage 2), the output is English. Do I misunderstand anything?

and Stage II, it starts with selected language. Keymap need to keep in English, default is English.

For some Asian languages, such as Chinese and Korean, the default keymap is English. But for some ones like Japanese, the default one is their relative keymap such as Japanese keyboard. So the cases were designed to test the appropriate keymap and if it's selected as default.

Replying to [comment:15 rhe]:

for Asian Languages, we need to add few steps, if user is using boot.iso or network install, then Stage I (anaconda) installer, Asian languages are using English text

Yeah, but I think for every language and media, before language selection step(stage 2), the output is English. Do I misunderstand anything?

The only situation different situation I can remember regarding this is when you compose a localized spin. In those situations the language is defined via kickstart before the language selection step in Anaconda. Otherwise, the output is in English before that step AFAIK.

and Stage II, it starts with selected language. Keymap need to keep in English, default is English.

For some Asian languages, such as Chinese and Korean, the default keymap is English. But for some ones like Japanese, the default one is their relative keymap such as Japanese keyboard. So the cases were designed to test the appropriate keymap and if it's selected as default.

The important in this case is to make sure that once the language is set then the appropriated keymap is automatically pointed by Anaconda, whether it is an English keymap or not.

I updated the test cases in [1] in order to improve the tests coverage. I added some post-install steps related to things defined during the installation. For instance, testing if the the root password matches the password set during installation. Other steps are to make sure that different applications are "understanding" the keymap defined by Anaconda.

[1] https://fedoraproject.org/wiki/Category:I18n_Installation

Replying to [comment:17 igor]:

I updated the test cases in [1] in order to improve the tests coverage. I added some post-install steps related to things defined during the installation.

Thanks Igor, I've seen your changes, the post-install check is essential, and it also has a better coverage now.

For instance, testing if the the root password matches the password set during installation.

Any particular reason why [https://fedoraproject.org/wiki/QA:Testcase_Asian_Language_Install Asian Language install] didn't have this step? AFAIK, it's the same as other cases, so I updated the case with this step and its expected result, hope you don't mind.

Thanks,[[BR]]
Hurry

Replying to [comment:18 rhe]:

Replying to [comment:17 igor]:

For instance, testing if the the root password matches the password set during installation.

Any particular reason why [https://fedoraproject.org/wiki/QA:Testcase_Asian_Language_Install Asian Language install] didn't have this step? AFAIK, it's the same as other cases, so I updated the case with this step and its expected result, hope you don't mind.

That was by bad Hurry, thanks for correcting it. This step was supposed to be present in all test cases but I missed that one.

Now we are in a good place for the test day. Is there anything else left that we need to take care?

Regards,
Igor

Replying to [comment:19 igor]:

Now we are in a good place for the test day. Is there anything else left that we need to take care?

Thanks to you, this test day has been well prepared, and I think the only thing left is to ask for collaboration. I'll send announcement to test-list and local community one day or two before the test day time. Please also announce it in your team or post it somewhere in advance. Thank you!

Today I've sent announcements to -trans and LATAM lists. I also requested them to relay the message to local translation teams.

Replying to [comment:21 igor]:

Today I've sent announcements to -trans and LATAM lists. I also requested them to relay the message to local translation teams.

Thanks, I've also sent it to test-announce and local list. I talked with Jens earlier and he already forwarded the announce to i18n list. Hope we can have a good testing day.

Test day was carried out successfully and Igor has sent out the test day recap:

• http://lists.fedoraproject.org/pipermail/test-announce/2010-September/000133.html

Closing this ticket, thanks everyone.