VCLTesttool 2.4

From Apache OpenOffice Wiki
Revision as of 16:18, 2 September 2007 by Tbo (Talk | contribs)

Jump to: navigation, search



Since the time got too short to introduce a new VCL TestTool for testing OOo 2.3 we will go on now at the beginning of the OOo 2.4 tree to get a new testtool.

We tested the CWS gh13 with all available test scripts. Now we want to use the VCL TestTool based on SRC680m226 as the new default testtool for OOo 2.4. It is currently declared as beta version.

Beta testing

Since we found almost all regressions by testing the CWS gh13 we will reduce testing for this version. In the beta testing phase Hamburg qa automation team will run the next master category test on the platforms for SRC680. It will take some time to start and evaluate the results, since OOo 2.3 is currently tested for release. Everybody else may also test the testtool version and report errors regarding the VCL TestTool application.

The binaries succeded the first.bas and topten.bas tests.

Currently existing downloadable VCL testtool binaries (SRC680m226) These are standalone VCL TestTool binaries.

  • Solaris Intel (Master tester MSC)
  • Solaris Sparc (Master tester JSI)
  • Linux (Master tester FHA)
  • Windows (Master tester HDE)
  • MacOS X PPC Aqua (Tester needed)
  • MacOS X Intel Aqua (Tester needed)
  • MacOS X PPC X11 (not tested, since it will get deprecated.)

After the testtool is declared as final, this version will be used by Hamburg qa team, and it is the reference for everybody else; If you find a bug or issue with an testtool other than the final testtool version you have to verify if it also comes up with the reference testtool.

Errors found during beta testing

Please insert the issues here.

Finished testing

Insert finishing date here and announce in qa-dev

Check list

  • create standalone binaries (TBO 03.09.2007)
  • run topten.bas and first.bas
  • checkin changes to standalone version
  • verify testtoolrc and insert timeout of 4 minutes
  • write stand alone testtool wiki entry
  • upload binaries
  • announce in qa-dev
  • Wait for feedback of master testers
Personal tools