Maho: I would like to add this: Get rid of the 'weird' methods used in the testtool and its scripts. It is very interesting looking though how a button is pressed on a screen to see the results...(Yes I read through the scripts). Also, there are serious changes that need to be incorporated for the MacOSX builds because there are there are differences in the number of items and the results of some of the tests that are valid for the Mac versions but not for other versions.
Also, I plan on converting testtool and the scripts from German to English and changing them for the Mac. This is long overdue for an international effort. Jogi: Please do not take offense to the above, this is just an observation that the scripts are serving their purpose for the Hamburg engineers at SUN but not for this project which supports more than just Windows/Linux/Solaris. I would not want to start a us vs. them fight, but if we can do platform independent work and get this incorporated into testtool and working, that would be great. James McKenzie -----Original Message----- >From: Maho NAKATA <[EMAIL PROTECTED]> >Sent: Feb 7, 2007 5:37 PM >To: [email protected] >Subject: Re: [qa-dev] Testtool script for ooo 2.2 > >Dear Joerg, > >From: Joerg Sievers <[EMAIL PROTECTED]> >Subject: Re: [qa-dev] Testtool script for ooo 2.2 >Date: Wed, 07 Feb 2007 10:19:02 +0100 > >> We have started testing yesterday -> see Wiki Matrix [1]. >> We will find showstoppers, problems etc. It is impossible >> that these are the final sets. > >This is a problem. When it becomes final, and/or >when we (outside Hamburg) can include fixes? >For example, Joerg can say this is the final, but for MacOSX and in terms >of l10n, this might not be a final one; there might exist show stoppers. > >> Does it really make sense to put them in an archive? We have had in the > >There are two intentions, one is Andre explained completely; >lowering the barrier. This is a real barrier. That's why I used `zip' >not tar.gz or tar.bz2. This is for Windows users. >Second, users should use the same script. >Some are checked out from trunk, and some are fixed l10n issues >by theirselves, in such a case we cannot analyze the results. >If we use the same script, we can analyze which part failed systematically. > >> past a set of final test scripts on the project page. Is there a need to >> have them in an archive? > >> [1] >> http://wiki.services.openoffice.org/wiki/OOoRelease22AutomationTestMatrix >This is a great one, thank you. > >All the best, >-- NAKATA, Maho ([EMAIL PROTECTED]) > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
