[dev] Questions about qatest failures
Hallo, I've run the ooo_releasetests.sh on my own build of OOo 2.1 and I have some questions about the tests that failed. The first failure is tGallery_CheckNames - check the number of gallery-themes Warning: Difference in count of gallery themes; found: '6'; expected: '30' - check the names of gallery-themes file for comparison is : /ooo/qatesttool/graphics/update/input/gallery/gal_49.txt I've checked several other OOo installations (from the PrOOo Box) on Linux and Windows. In every case the Gallery had only the 6 entries Begrenzungen, Bullets, Eigenes Thema, Hintergründe, Homepage and Klänge. Where are the other 24 themes supposed to come from? The next failure (well, not technically a failure) is tHelpCheckForUpdates This could be a (patched) OOo installation on Solaris Sparc/Intel - No Online Update Feature available. This used to be tHelpCheckForUpdates Warning: Online Update Feature isn't available in this build? (no 'UpdateURL' in file: '/opt/openoffice.org2.1/program/versionrc') then I entered UpdateURL=http://update.services.openoffice.org/ProductUpdateService/check.Update in versionrc and it turned into the message about a patched OOo installation. I've checked the OOo from the PrOOo box. The Windows version has the Check for Updates item in the Help menu, but even after entering the above URL in versionrc the Linux version 2.1 and 2.2 from the PrOOo box don't have the Check for Update item. Is this normal? What are (aside from the UpdateURL) the conditions that have to be met for the menu item to appear under Linux. Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Questions about qatest failures
Hi Matthias, I would like to invite you to the mailing list dev@qa.openoffice.org for further questions regarding VCL TestTool application and tests. Answers inline... Matthias B. wrote: Hallo, I've run the ooo_releasetests.sh on my own build of OOo 2.1 and I have some questions about the tests that failed. The first failure is tGallery_CheckNames - check the number of gallery-themes Warning: Difference in count of gallery themes; found: '6'; expected: '30' - check the names of gallery-themes file for comparison is : /ooo/qatesttool/graphics/update/input/gallery/gal_49.txt I've checked several other OOo installations (from the PrOOo Box) on Linux and Windows. In every case the Gallery had only the 6 entries Begrenzungen, Bullets, Eigenes Thema, Hintergründe, Homepage and Klänge. Where are the other 24 themes supposed to come from? That is because the test writer assumed that he always has a StarOffice version to test ;-) He updated his test for OOo 2.2 and SRC680: on 14.12.2006 http://qa.openoffice.org/source/browse/qa/qatesttool/graphics/update/inc/global/gallery.inc?r1=1.16r2=1.17 The change wasn't done for the tests in the branch for OOo 2.1 I will ask him, if he will do it for OOo 2.1 also... The next failure (well, not technically a failure) is tHelpCheckForUpdates This could be a (patched) OOo installation on Solaris Sparc/Intel - No Online Update Feature available. This is just a black on white message? That is correct, because the feature is disabled in selfmade OOo builds. It is just enabled in Sun provided developer builds if I remember correctly. This used to be tHelpCheckForUpdates Warning: Online Update Feature isn't available in this build? (no 'UpdateURL' in file: '/opt/openoffice.org2.1/program/versionrc') Hmm, strange, the test shouldn't come to this point. It would mean - Help-Check for updates is enabled or - The slot that TestTool calls succeeds, even if the menu item is disabled. then I entered UpdateURL=http://update.services.openoffice.org/ProductUpdateService/check.Update in versionrc and it turned into the message about a patched OOo installation. I've checked the OOo from the PrOOo box. The Windows version has the Check for Updates item in the Help menu, but even after entering the above URL in versionrc the Linux version 2.1 and 2.2 from the PrOOo box don't have the Check for Update item. Is this normal? What are (aside from the UpdateURL) the conditions that have to be met for the menu item to appear under Linux. How to get this Update feature enabled is described in: http://specs.openoffice.org/appwide/onlineupdate/Software_Update.odt Matthias Cheers, Thorsten -- *** Thorsten Bosbach Sun Microsystems GmbH Quality Assurance Engineer 20097 Hamburg, Germany - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Questions about qatest failures
On 2/12/07, Thorsten Bosbach [EMAIL PROTECTED] wrote: Where are the other 24 themes supposed to come from? That is because the test writer assumed that he always has a StarOffice version to test ;-) He updated his test for OOo 2.2 and SRC680: on 14.12.2006 http://qa.openoffice.org/source/browse/qa/qatesttool/graphics/update/inc/global/gallery.inc?r1=1.16r2=1.17 The change wasn't done for the tests in the branch for OOo 2.1 I will ask him, if he will do it for OOo 2.1 also... Thanks, but all that I wanted to know is that there's not some hidden switch I have to set at build time to get more themes. How to get this Update feature enabled is described in: http://specs.openoffice.org/appwide/onlineupdate/Software_Update.odt That's where I got the UpdateURL from. It says The visibility of the new menu item Check for Updates... will be triggered by a new key entry in the version.ini|rc files. The key is called UpdateURL and should provide a valid http URL to the update server. The menu item will be visible if this key has a value, otherwise menu item will be hidden. The following line illustrates the new key in the version.ini|rc file: That's why I'm surprised that setting the UpdateURL does not make the item appear (on Linux). Apparently there's more to it than is written in the specification. Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
