Automated tests on release candidates have been finished and all results of automated tests are green state. All Cat0-Tests required for a release finished without errors or warnings (except #108549 on MAC) testing english language builds. See the following graphics for details:

Enjoy OpenOffice.org 3.2 once released....

tags: automated_tests qa

Automated tests on milestone OO320m7 are finished. Automated testing team reported a 'green state' for all automated tests. Just a small problem in w_updt.bas bother the consistent picture of all platforms marked green in QUASTe. This issue wasn't easy to find but at the end we solved the problem in showstopper CWS 'jl146' with issue 107038. Depending on desktop respectively OpenOffice.org window size the document is middle or left aligned with automatic view layout (which is default). This lead to the problem sometimes the objects in writer document were drawn outside of the documents area by autotest. Finally we found and fixed it by correcting view layout before testcases run. Some additional minor fixes for more stability were also done in this CWS. Punctually with release of RC1 next week the autotests are expected to deliver a 'green state' on initial testrun.

Stay tuned for updates on this....

tags: automated_tests qa

As promised the results of automated tests for release workspace OOO320 starting minor m3 to m4. Explanation of testresults from OOO320m1 to OOO320m2 can be found here. As expected in previous blog the m3 had a green state as all features covered by automated tests had no issue. But unfortunately Issue 106678 put a spoke on our wheel and shredded all results in OOO320m4. Thats why this high number of errors and warnings made this build from our point of view useless. The reason why this issue wasn't found by automated tests in CWS impress180 is currently unknown. However see the graph on quality progress:

tags: automated_tests qa

Automated testing of recent OOO320_m1-OOO320_m2 builds is finished. All Cat0 tests were run on English builds by automation team and have been completed. On OOO320m2 there is 1 warning only in automated tests (105967) except on MacOS we have 2 errors and 3 warnings (generated by issue 105275). Issue 105967 is handled in CWS automation320m2 and issue 105275 in CWS impress178. Green state of automated cat0 tests is expected with integration of those CWS'.

The high VTTDI-value is due to an issue 105962. This hinders f_first.bas to be added to QUASTe which is a regression in automated test and is expected to be fixed with integration of CWS automation320m2 also.

See trend created from testresults stored in QUASTe

Stay tuned for updates on testresults.....

tags: automated_tests qa

With availability of Milestone m1 on branch OOO320 (OpenOffice.org 3.2) automation team - as always on a way to a release - starts to test each milestone based on a matrix.
Autotests were made more stable in the past weeks and are now prepared to run 'Greenstate' for this release. In case of errors found by test scripts beginning with m1 they have to be close analyzed as they may be failures in OpenOffice.org. Please contact script owners if an error was found and you need help to analyze. For all potential errors in test scripts a CWS will be created to fix them and have fixes available in following milestone. Of course main goal is to assure OpenOffice.org remains free of issues for QA automation purposes.
All results of automated tests are collected in QUASTe[1] and are available to everyone to see what has been tested. An overview of what should be tested one can take a look on the matrix[2]

English installsets are tested with automated tests of category 0 by SUN automation team[3] with tests of Category 1-3[4] by module owners[3] on selected platforms and languages.

All community members are invited to run automated tests on platforms and languages of their choice. This should be tests of category 0 at first. See matrix what selection fits best to you.

If you have any questions please contact dev@qa.openoffice.org or responsible testers.

Thanks for your support.

tags: automated_tests qa

tags: automated_tests qa quality

With "normal" setup installation it is currently not possible to have more than 1 OpenOffice.org installed on the same windows system in parallel. But for testing purposes it is really necessary to have more than 1 installation available to e.g. check for regressions. For those who looked over the readme.txt coming with the installation set might have been stumbled over the so called 'Administrative installation'. This kind of installation is used to put an installation on a network drive for example to let it be reached within a network. This of course can also be used to 'install' an OpenOffice.org to your local drives. The only disadvantage is you don't have any system integration like registry or menu entries or quickstarter enabled. But if you plan not to test or use those features it isn't required to have a full system integration and also not if you plan to run automated or manual tests based on office features.

Get started:

Installation:

Lets say you've downloaded the (currently) latest OpenOffice.org in version OOO310m9

• Simply extract the archive to a location of your choice (use for example "C:\OpenOffice.org 3.1")
• After all files have been unpacked the 'Installation Wizard' starts => Please cancel it
• Click Start->Run and enter "C:\OpenOffice.org 3.1\setup.exe" /a
  
• Press 'OK' button to execute 
• Now that the 'Installation Wizard' started again please press 'Next'
• On second page please enter the target location ( use for example "C:\test\OOO310m9" )
• click 'next' and wait until installation has been finished

To have installation more comfortable without any user interaction one can use 'msiexec' to install OpenOffice.org. Simply use the following syntax for an administrative installation into a directory of your choice: "msiexec.exe /a  {OpenOffice.org-sourcedir}\openofficeorg31.msi /quiet /qb TARGETDIR={OpenOffice.org-targetdir}"

Tipp: To manage your installations easily one could create some links to different installation directory's on your desktop for example.

Adapt directory for user settings

Each installation must use a different directory for storing user-settings to avoid unmeant effects. This can easily be done by adapting an ini-file called 'bootstrap.ini'
(to be found in directory "C:\test\OOO310m9\OpenOffice.org 3\program\" of your previous made installation)
Simply change the string found for key 'User Installation' in area [Bootstrap] to a path of your choice. In this example we use "C:\test\OOO310m9".

If you now start the OpenOffice.org by executing "C:\test\OOO310m9\OpenOffice.org 3\program\soffice.exe" it uses it's own user-directory.

Adapt changes for automated testing

If you plan to use an installation for automated testing with VCLTestTool please check Wiki-page to learn what settings must be made. To let VCLTestTool find the administrative installation it is required to adapt an option named 'OOoProgramDir'. Simply change this to the program-dir of your OpenOffice.org Installation like "C:\test\OOO310m9\OpenOffice.org 3\program" in this example

Enjoy !

tags: automated_tests qa

Automated testing of recent OOO310_m9 builds is finished. All Cat0 tests were run on English builds by automation team and have been completed. 1 warning on Solaris was submitted. This shows up because of issue #100780 This warnlog will be removed on next milestone ( #100809 ) because it'll be fixed not until OpenOffice.org 3.2

See the trend created from testresults stored in QUASTe

Cat 1-3 testing on release candidates

With availability of milestone OOO310m9 automation team starts testing of Cat1-3 tests on english language followed by updated release matrix. As always all members of localization teams with skills in automated testing are invited to test the localized builds and add their results to QUASTe. Thanks for your support.

tags: automated_tests qa quaste

Automated testing of recent OOO310_m8 builds is finished. All Cat0 tests were run on English builds by automation team and have been completed. All automated tests created the same results as in previous milestone except on MacOS. Here a stopper (Issue 100667) has been found and lead to incomplete testresults. This will be fixed within next milestone.

See the trend created from testresults stored in QUASTe

tags: automated_tests qa quaste

Automated testing of recent OOO310_m6 builds is finished. All Cat0 tests were run on English builds by automation team and have been completed. The trend is absolutely clear the OOO310 version is getting much better and stable from the view of  automated tests. Currently we only have 1 problem on linux and 1 problem on MAC in each case. These problems are identified in testscripts and a fix is available.

See the trend created from testresults stored in QUASTe
VTTDI-Index

Let's keep up the trend.....

tags: automated_tests qa quaste