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 really need _one_ set of instructions that I can work through. >> >>> >> Testtool does not care about the language, it cares about the >> functionalities. Thus you should be able to use the Vietnamese >> (.vi.dmg) files and have no problems with testtool running. I will >> note, however, that the Base tests, and especially the Datattypes >> tests, will not work properly if you use the qatesttool files >> provided from OpenOffice.org. The Mac version does not support >> several types of databases that are tested by this test. I sent >> you an updated test file for your usage. > >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. >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. >> Great. TCM is for localized testing and to observe that all >> functions do work as they are supposed to. > >But TCM also involves running testtool. They are not separate >processes. The automation tests in TCM use testtool. They are all I >have left to do of the release-sanity scenario. >I have done that. 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 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... > >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. James McKenzie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
