>From: NAKATA Maho <[EMAIL PROTECTED]> >Sent: Dec 15, 2006 11:47 PM >To: [email protected], [EMAIL PROTECTED] >Subject: Re: [qa-dev] QA of OOo 2.1RC2 Japanese MacOSX Intel > >From: Clytie Siddall <[EMAIL PROTECTED]> >Subject: Re: [qa-dev] QA of OOo 2.1RC2 Japanese MacOSX Intel >Date: Sat, 16 Dec 2006 14:45:38 +1030 > >> > 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 > >> Also, can you go on using your Mac while testtool is running? (If >> not, 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. > >> I don't know if this version is available for Vietnamese. If not, can >> I use the build for another language? > >?? please use *vi.dmg or something like that. I think ISO code for your >language 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. > >> 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. > >> 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. > >Please ask NL lead of vi about it. You can accumlate failures, bugs etc and >raise issues. Otherwise they are not visible. and bugs are fixed by developers >in the community member. If developers are not available, that's a problem. >I'm very sure that there are many great hackers in vi community. > >NL lead or QA people assgined by NL lead can mark as `release' even though >you don't do some test, though ;) > If an item fails TCM testing, you should raise an issue unless an issue already exists. 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. 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. James McKenzie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
