#14 Test Day for iBus (2009-05-14)
Closed: Fixed None Opened 14 years ago by petersen.

The fedora-i18n team would like to propose an ibus test event:

https://fedoraproject.org/wiki/Test_Days:IBus

tentative date 14th May though ideally earlier.


Briefly discussed over email with petersen several topics. Including snippets below ...

Thank you for creating the iBus Test Day request. As you have
noticed, the F-11 Test Day schedule is fairly booked at this point.
However, I would like to accommodate your request.
Great! Do you think it is best to wait until 14 May (it is very late in the cycle)?

Unfortunately the time slots are fully booked leading up to, and following, the preview release. The May 14th time slot is after the final F-11 compose so it is unlikely that any bug fixes would land in the F-11 physical media kit (CD/DVD). However, this could be used to gather fixes for a day-0 post GA ibus update?

Who should I contact to represent QA
Contact Lawrence Lim

Are there public lists we should include in the announcement of this event?

fedora-l10n is probably a good place to advertise as well as fedora-i18n of course.

Just a ping, we are coming up on 2 weeks for the upcoming iBus test event. I'd like to outline what tasks remain to ensure this event is successful. Can you help me complete this list?

{{{
OWNER TASK
===========================================================================
[jlaska] - Announce event to fedora-{devel,test}-list@redhat.com
[ ] - Announce event to ibus community list(s)
[jlaska] - Reach out to Red Hat and Fedora i18n teams
[ ] - Prepare wiki-style test cases [1], [2]
}}}

So far the wiki page looks great. I think the only outstanding item is to create several wiki-style test cases that people can log test results against. Do you have any other thoughts/concerns?

Thanks,
James

Replying to [comment:4 jlaska]:

[jlaska] - Announce event to fedora-{devel,test}-list@redhat.com

Great! - please also include fedora-i18n-list and fedora-trans-list.

[phuang] - Announce event to ibus community list(s)

phuang will forward your fedora announcements to the ibus community.

[jlaska] - Reach out to Red Hat and Fedora i18n teams

Tagoh will coordinate with CIJK fedora-trans-* teams to get announcements out in their local mailing lists.

[ ] - Prepare wiki-style test cases [1], [2]

Ok, I will take this: will try to have something ready by early next week.

Do you have any other thoughts/concerns?

No I don't think so. Thanks, Jens

James, would you be able to prepare Live images for the day? :)

We improved the test page quite a lot: the testcases should be finalised tomorrow.

Updated list of tasks

{{{
OWNER TASK
===========================================================================
[jlaska] - Announce event to fedora-{devel,test}-list@redhat.com
[phuang] - Announce event to ibus community list(s)
[Tagoh] - Reach out to Red Hat and Fedora i18n teams
[petersen] - Prepare wiki-style test cases [1], [2]
[jlaska] - Prepare test day live images 2 days prior
}}}

One note, when creating test cases on the wiki, please use care and do not edit the test case template directly. You'll want to click the ''edit'' link at the ''top'' of the wiki page, not the ''[edit]'' links near each section.

Just adding a little more detail:

{{{
OWNER TASK
===========================================================================
[jlaska] - Announce event to fedora-{devel,test,i18n,trans}-list@redhat.com
[phuang] - Forward announcement to ibus community list(s)
[tagoh] - Reach out to Red Hat and Fedora l10n teams
[petersen] - Prepare wiki-style test cases
[jlaska] - Prepare test day live images 2 days prior
}}}

I sent a mail to the RH L10n Team leads in Brisbane and Pune today reminding them of the event next week and calling for the participation of their teams.

Replying to [comment:9 jlaska]:

One note, when creating test cases on the wiki, please use care and do not edit the test case template directly. You'll want to click the ''edit'' link at the ''top'' of the wiki page, not the ''[edit]'' links near each section.

Oops, sorry about that - it might be better to make the template immutatable to avoid such problems reoccuring, since it is a little confusing for new people.

Replying to [comment:11 petersen]:

Oops, sorry about that - it might be better to make the template immutatable to avoid such problems reoccuring, since it is a little confusing for new people.

No worries, it's an easy mistake (speaking from experience :) ). I would like to make that page immutable but wasn't able to find out how. I'll ask around today for more information. Thanks for the tip!

Adding lili to the cc list who will be helping out from the Fedora QA side of things.

Replying to [comment:12 jlaska]:

Replying to [comment:11 petersen]:

Oops, sorry about that - it might be better to make the template immutatable to avoid such problems reoccuring, since it is a little confusing for new people.

No worries, it's an easy mistake (speaking from experience :) ). I would like to make that page immutable but wasn't able to find out how. I'll ask around today for more information. Thanks for the tip!

Update ... the Fedora infrastructure group has marked the template as read-only. So we shouldn't have any more troubles editing pages.

James,

Can we get an anounce mail earlier than the test day (well, today or tomorrow) so that we might have more people in IBus community or internal testing?

I meant to forward it to the certain list.

Replying to [comment:15 tagoh]:

James,

Can we get an anounce mail earlier than the test day (well, today or tomorrow) so that we might have more people in IBus community or internal testing?

Liam posted the iBus announcement yesterday (see https://www.redhat.com/archives/fedora-test-list/2009-May/msg00444.html). Thanks Liam!

There are already a few questions on the list, you may wish to help answer if you have time.

I have also forwarded Liam's mail to fedora-{i18n,trans)-list
* https://www.redhat.com/archives/fedora-i18n-list/2009-May/msg00000.html
* https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00078.html

Additionally, live images have been created using ibus-1.1.0.20090508-1.fc11. These images have been uploaded and the Fedora wiki updated with links.

Adam Williamson will be posting a blog announcement later on today.

Thanks everyone for the good successful test day!

Replying to [comment:18 petersen]:

Thanks everyone for the good successful test day!

Thank you Jens! After your request, we put a call out for more testing from European lang+keymap users. Was this successful?

Also, looking at the [https://fedoraproject.org/wiki/Test_Day:Current#Test_Cases_and_Results wiki] it appears gathering results was well received. Do you have a high-level summary of results from the event, I'm interested in your feedback as to what worked well and what needs improvement?

Thank you Jens! After your request, we put a call out for more testing from European lang+keymap users. Was this successful?

Well very few non-Asian testers. I think mcepl starting working on a cs (Czech) input map for m17n though. :)

Also, looking at the [https://fedoraproject.org/wiki/Test_Day:Current#Test_Cases_and_Results wiki] it appears gathering results was well received. Do you have a high-level summary of results from the event, I'm interested in your feedback as to what worked well and what needs improvement?

Yes it was very useful. We filed a bunch of bugs for for the ibus engines and got valuable feedback on ibus usage, particular from our native translators.
So it was a very beneficial event for ibus I would say.

Do you have a high-level summary of results from the event,
I'm interested in your feedback as to what worked well and what needs improvement?

We could provide a list of bugs I guess - most of them should be linked from the page by now hopefully. Most of the testers were from redhat's localization team. It would be good if we could get wider participation and more detailed testcases in a possible future testday.

Ooops, this ticket was left open. Closing out as this was a F11 test day.

Login to comment on this ticket.

Metadata