--> You are now talking on #ooonlc --- チャンネル #ooonlc のトピックは Next IRC-meeting [L10N automated testing] scheduled for February 08, 2007 - 12:00 UTC time | For agenda see http://wiki.services.openoffice.org/wiki/IRC_Meetings です チャンネル #ooonlc のトピックは Thu Feb 8 20:20:57 2007 に Thalion72 によって設定されました #ooonlc :[freenode-info] if you're at a conference and other people are having trouble connecting, please mention it to staff: http://freenode.net/faq.shtml#gettinghelp friede1 は friedel にニックを変更しました --> MechtiIde (n=Mechtild@87.139.60.106) has joined #ooonlc Well... it's already 12:00 UTC but I believe we should wait some minutes before starting. Hi all, asrail Hi maho Hi everybody. Do we have a detailed agenda yet? It looks like we won't have a strong audience. friedel: To revise the action list is on the agenda and I proposed RCs testing on TCM, if no one have any objection Acronym dictionary somewhere? friedel: Release candidates or Test Case Management? Thanks Hi all Hi Hello Two more minutes and we start the meeting... --> Thalion72 (n=sca@adsl-89-217-134-197.adslplus.ch) has joined #ooonlc Let's start ok The topics on the agenda are: - Review of action items - Release Candidate testing on TCM - Q&A Someone has some other suggestion? OK. Let's start the review of action items 1 - Promote use of the use of TCM and QAtrack tools on the l10n lists owned by Rafaella and all seems not to be done yet but it should be done as soon as possible I would like to see more l10n members here to discuss this well .. this is a ongoing task, not a one time item for sure... Let's skeep to the new items... 2 - "howto localize testtool environment at the wiki (att information about mandatory and recommendet tasks) owner Andre Schnabel I've seen strong activiy on Issue Tracker.... well .. not strong but it' ongoin Thalion72: OK. Any l10n or QA help needed? most of the update tests are documented, framework tests are missing i was happy if any l10n tam could start reading the wiki page and try to get their localized tests running ... .. just t see if my notes are usefull Great, we can promote this on the mailing list there is still one open question about gallery tests Thalion72: What question is this? http://wiki.services.openoffice.org/wiki/HowTo_localize_qatesttool_environment#Graphics_.28Draw.2C_Impress.2C_Gallery.29 ... last point I asked @ dev@qa .. but no answer yet Ah, OK. The next item is: 3 - Provide information about creating and test result information system (taken from Google Summer of Code suggestion) owned by Jog Jogi I haven't seen anything about it. Someone has any new on this topic? unfortunately Jogi cannot attend to this meeting. I'll ask him. ja_: thanks Next item is: 4 - provide documentation about localization support in testtool scripts owned by Fredrikh It's another one who couldn't attend to this meeting... We can ask this on the list after the meeting too. 5 - provide documentation, who to file isses for testscripts owned by Andre Schnabel not done will do within the days at the wiki ok This was the last action item with the "new" state Is there any suggestion of a new action item? usually the creator of the test script can be read from the header of each test script right, but if .ods case? http://www.openoffice.org/issues/show_bug.cgi?id=74680 ja_: yes ... but this should be documented somewhere ;-) for example ja_: "maintainer" ;) asrail: +1 OK Let's move to the next topic: maho: ok, will add some notes about files, that have no visible "maintainer" - Release Candidate testing on TCM Thalion72 : please feel free to re assign this to me if you are overloaded The announcement is done by Naoyuki AFAIK, this is cws localization19. I would like to have info about when the TCM tests will be triggered As he says, TCM l10n testing is not acceptance testing but finding l10n issues as much as possible maho: and he is correct with that ja_: Do you have any info on this? maho: but the idea is / was to use TCM for acceptance testing as well. right thalion72: right that's why the term "TCM test" is incorrect (sorry phone) ;) asrail: 'TCM' tests should start even if there will be a second release candidate. Right. But not setuped yet. Who takes this decision? Naoyuki? can we speak about l10n test (done for CWS builds) and release tests (done on RC)? I'll ask Rafaella They already should have been triggered Thalion72: Yes, we can. ja_ / all: imo the release tests should be triggered as soon as the first RC is available right. builds are available I thought that announcement by ja automatically trigger QA but there are two questions (from the past): who creates the "version" in TCM? maho: that was my assumption ;) maho: It should me too - for MacOSX packages 2nd: do we use one version in TCM for all RC's or one per RC? all RC's. one per RC exhasts testers also - In rc process, nothing new features are introduced. only fixes showstoppers Yeah... only the tests where something's changed should be redone so - if showstoppers are identified, we can ignore some tests and still whole office is functional maho: correct of course, one per RC is ideal. Thalion72: I think Naoyuki and some other guy at Sun "creates" this version asrail: well .. there are several people who can actually do this ;-) the question is "who is in charge" Thalion72: I've email'ed Rafaella to care about this Thalion72: It's hiden somewhere deep inside Sun ;) Ah! MGR role is insufficient? Thalion72: she'll probably ask Naoyuki directly asrail: there is no need to hide this inside sun ja_ : okay maho: you need to be MGR for en Thalion72: I would rephrase it It shouldn't be hiden inside Sun (you, Joost and Caio should know the password) Thalion72: I'll ask naoyuki. also - Caio too ok ... so for 2.2 ... I can create the version but I do not feel "in charge" I should. maho: ok .. I'll give you the account data and a short "briefing" ... Thanks. (if you have some minutes after the meeting) OK So it should be clear who is in charge of creating the versions on TCM and Rafaella and Naoyuki can provide us the info ja already emailed her... Is there any further discussion on this topic? we still need good acceptance tests .. but I have no idea how to get them mmm the current tests in the release sanity scenario ar still more usefull for localization than for acceptance right. but afaik, there is a rework of the qa teams ongoing .. maybe the new temas could provide some bsic tests (within the next months) Some of these acceptance tests only would need to be mades on one platform ops s/platform/language TCM does not handle this difference very well hmm .. I think TCM is able to handle different scenarios per language but never tried to setup such a scenario I'll ask Naoyuki about this issue. anway .. I think, we can work on this later. Thalion72: I believe it is not able to handle one scenario where members of each language could update the reports asrail: ah .. correct .. reports are different es members can update es scenarios and so on probably Naoyuki has an idea how to improve this So... it's bounded to languages and not all tests that could be made fit into this category ja_: We can ask him too Let's move to Q&A? So... next item is: - Q&A when QA script in ooo220 became the final? maho: I believe there is no need to became "final" But it would be good to assign some snapshot of them with the builds Hm, idally, criterion for approval is no errors! asrail: there is a need, as we do not know if we test OOo or if we "test the testscripts" Thalion72: lol asrail: but this doesn't mean, that it is realistic to get the "final testscripts" ;-) Thalion72: They should be mature, without known errors. But I believe they could be updated in case errors are found while testing some build By the way... we should "test the testscripts" Not on this stage, of course we also should test for MacOSX, too. asrail: right. we are not on this stage. asrail: I'm actually doing this ;-) but I don't believe they are widely tested on all languages and platforms but with low priority Thalion72: Doing the job of documenting it implies testing... but there could be some issue with Japanese, for instance asrail : in my impression, I agree with you correct I encountered several problems with the scripts while testing vietnames localization I've just talked to Helge Delfs (one of the full time automation engineers). He said that it's quite impossible to say "This test script version tag is final" before the version has been released. Today he eg. found an error whilst testing the russian version. That's why I said it is not needed Is a lot more important to test them ja_: I agree .. but this doesn't mean there is no need ;-) (and some needs will never be fullfilled .. so what) We are going to a circular dependency :) ...and he said that the scripts should be at least good enough to work with them the bug he found with the ru version has been fixed ja_: yes, that's true. The scripts are good and only few errors occur. So- actually russian version doesn't contain bug but testscript. ? Thalion72 : Thorsten Ziehm told that `Because all tests should run without any error! ' maho: and that's true I mean, the russian version of RC1 doesn't have an error, but actually testscript had an error. sorry, misunderstand. maho: ...that has been fixed Is there any other open question? I confused, ` the russian version of RC1 doesn't have an error, but actually testscript had an error' is right? ja_ maho: yes thanks. Well... Since almost everyone here is of the QA team... I would like to propose a meeting at #qa.openoffice.org, same time, on two weeks. +1 We will have more QA than NL questions around that would be March 8th - 12:00 UTC +1 ok It would be great if Naoyuki, Jogi, Rafaella and others could joing us Yes. I'll send them a mail asking for this... if that to be shown a bad date, we can choose another one If everything goes fine, we'll have a meeting March 8th - 12:00 UTC on #qa.openoffice.org thanks asrail. welcome The meeting is, officially, over Thank you all for attending thanks all thank you