Re: [qa-dev] Testttool on the Mac Intel

[Clytie Siddall]

Hello all :)

Another day, another try with testtool.

James, thankyou for your reply.

On 18/12/2006, at 2:00 AM, James Mckenzie wrote:

Got a lot of trimming to do here...

Was this in Uwe's doc? I don't think so. I am confused now. I don't
know where to go from here. "Here" is up to running the first test in
Uwe's doc. I did everything up till there, I think. I didn't get

files from CVS because I used the testtool link in Maho's email instead.

Yes it is. However, Uwe states that you can run the testtool from version 2.0.4 onward from the testtool.bin file. Since you must use the testtool from 2.0.3 (it is broken in 2.0.4 and 2.1, see issue 69378 for more information) on the Intel platform, you must use the testtool script which is a copy of soffice renamed to testtool.

I think I did all that. I used testtool from 2.0.3, and I copied soffice to testtool.

Where do I put that file, please?

Put it in qatesttool/base/update/inc

This is what the QA team calls an include file and has the database type tests in it.

OK. I replace the previous file with this one. Last night, I didn't know that, so I just guessed and put the file in that dir. No replacement.

I asked about the language of the build, because Maho said use an
older version of OOo for testtool, but I'm not sure we had any
Vietnamese builds for versions before 2.1.

You can use the en_US version against your Vietnamese builds. It should work without errors.

That's what I used. It appeared to work, but the process only ran for three or four minutes then said FINISHED.

I've raised several issues for minor matters. No
major ones.

Here is a problem: You are the one that will determine if OpenOffice.org for Vietnamese passes QA or not. If you feel that a new user could not or would not use the product, it fails. If there is a major problem, it fails.

I was getting close to deciding the build was ready for release when I found out about the PPT export bug. :(

I passed the Intel build as I found no major functional problems. However, it does have a major flaw that I found out about after the fact, and that is with the install new dictionaries process. The window is too small...

So OpenOffice.org 2.1 for Mac Intel has been released? What about the PPT bug?

That's a useful guideline, thanks. Certainly the ppt export bug is
one of those flaws.

Actually, it also fails on my system. However, I have to look further into the problem to see what is causing the crash and if it is significant. If not, then the product passes. If it is something major, then the release was done too quickly and this is the problem with a timeline. Releases should happen only when they are ready, and not before. Putting a date on a release is totally against what I stand for.

http://groups-beta.google.com/group/vi-VN

I agree with you that fixed release dates are an artificial constraint, and in any case, three-month releases are absurd with a product of this complexity. We did discuss, on the releases list, changing to six months, and I thought that was going to happen. (Is it, do you know?) For example, I haven't got my OpenOffice.org 2.1 builds out yet, but the translation deadline for 2.2 is 18th January 2007! Only a few weeks away. So what do I do? Abandon 2.1 and work on the translation updates for 2.2? Finish 2.1 and not be ready for 2.2? We have a set of major goals for 2.2, including translating all the Help section (nearly half a million words) and improving support information in general. We'll be lucky if we get even the interface update in. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)

PGP.sig
Description: This is a digitally signed message part