On 21 Feb 2007, Thorsten Bosbach wrote: > I think you are referring to: > http://qa.openoffice.org/files/documents/77/3247/essen2006testtool2.pdf
Exactly. > The so called 'dialog test' in a non product / debug build checks for > truncated strings. It is a function in OOo, that is activated as shown > in the document: "Dialog test of OpenOffice.org" Quote: This test also shows whether controls overlap, whether the tab order is correct and whether the mnemonic characters are correctly assigned. I need to wait until my non-product build will be ready to test how this option will highlight normal and truncated strings. As far as I understand I need to review all screen shots made by testtool, right? > To ease this procedure, to get through all dialogs, you may use the > VCL TestTool. [...] > These scripts produce results, you have to read; If a string is cut > of, there is a colored message, telling you which one. Is there an example (error pattern) how I can grep truncated string errors and mnemonic errors from *.res files and easy find the corresponding screen shots (by hid I think)? > The 'documentation' ;-) is very short - it was in conjunction with a > presentation. So it is just an extract. I see. :) > If something is unclear, please ask ... Is "--enable-dbgutil" switch enough to get the non-product build? > Is there a direct link to the TCM testcase? Use this one: http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_testcase.cgi?tcm_config=newooo&action=query_testcase&product_id=1&category_id=9 Scroll down to the second test (Automation-2, test ID is 110030) -- Best regars, Rail Aliev http://{ru,tr}.openoffice.org The greatest of faults is to be conscious of none. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
