Resuming my quest to run testtool... On 17/12/2006, at 12:56 AM, James Mckenzie wrote:
4. OS specific settings; disabling screen saver and some tips.You have to do this to run testtool, or is this your own setting for other purposes?Yes. To run testtool. I don't write not relevant for QA test.Definitely you must clone soffice to testtool. Running testtool.bin WILL not work on the Mac Intel nor Mac PPC platforms for 2.1
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.
I really need _one_ set of instructions that I can work through.
Also, can you go on using your Mac while testtool is running? (Ifnot, I can run it when I'm not able to use it, so that's not a problem.)No, you cannot or it is not recommended. (that's why I jailed OSes in vmware...)You will quickly become very frustrated if you try. I recommend running this process overnight if you are on a fast Mac (G5 or Intel Mac). On my PBG4 it takes over a day to run the ooo_releasetest.sh series.
OK, I can run it overnight, if I can get it working.
I don't know if this version is available for Vietnamese. If not, canI use the build for another language??? please use *vi.dmg or something like that. I think ISO code for yourlanguage is vi.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?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.
And we report the results to this list? Nowhere else? What constitutes a pass in testtool, and what a fail?You can raise an issue like that: http://www.openoffice.org/issues/show_bug.cgi?id=71978 http://www.openoffice.org/issues/show_bug.cgi?id=70335(BTW: we are using testtool, but it is just my fad. I'm learning about TCM...)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.
If an item fails TCM testing, you should raise an issue unless an issue already exists.I have been uncertain whether a Fail in TCM is a serious matter or not. I have failed the build if it produces any reportable issues.
I have done that. I've raised several issues for minor matters. No major ones.
The fact that a portion of the program is not localized should not stop the release of the program, however, if you feel that an ordinary user would not use OpenOffice.org because of the flaw you found than you should also not recommend that the version be released.
That's a useful guideline, thanks. Certainly the ppt export bug is one of those flaws.
I did this for 2.0.4 because the Base Wizards were broken. It was discovered that this was a UNO bridge problem on the Intel platform and this function did work on the Power PC platform. I held the Intel release and authorized the Power PC release. Again, authorizing a release is a judgement call and should always have the 'ordinary' user in mind.
Indeed. Thanks. :)from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
PGP.sig
Description: This is a digitally signed message part
