Joost and Andre: As a MINIMUM, I recommend running the ooo_releasetest test set. On a slow machine, such as my PowerBook G4, this will take over a day AND YOU CANNOT NOR SHOULD NOT USE THIS MACHINE. On my MacBookPro this takes about eight hours.
If an error is encountered, run the test manually before reporting any problems. James McKenzie -----Original Message----- >From: Joost Andrae <[EMAIL PROTECTED]> >Sent: Jan 4, 2007 10:25 AM >To: [email protected] >Subject: Re: [qa-dev] Testtool & TCM > >Hi, > >it's really helpful to run testtool scripts for a release to assure that >resource files aren't broken. If they break of whatever reason then eg. >a dialog that makes use of this resource file will cause a crash. As >André already said at least someone might/should use first.bas and >topten.bas from ../framework/first/ for each build. Other tests can be >run on snapshot builds _before_ RC phase and (if there is much time...) >maybe on RC builds. RC builds are expected to be finished and only bug >fixes should get into those builds. > >Starting with the next developer snapshot build (to be expected within >the next days - maybe next week) we'll have a build that is (from >functional perspective) important to test for the upcoming 2.2 release. > >Have a look at > >http://wiki.services.openoffice.org/wiki/OOoRelease22 > >Kind regards, Joost > >--------------------------------------------------------------------- >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]
