Hi Thorsten,
I run all these scripts on 2.1 RC1 and RC2, and I didn't find the
truncated string that was really there in Basic IDE (see issue:
http://qa.openoffice.org/issues/show_bug.cgi?id=73263). There was no
message about that. So we're probably lacking Basic IDE checks? Or is it
possible that tests are too shallow?
I got an impression it's only sampling dialogs.
Regards,
Marcin
Thorsten Bosbach napisał(a):
Hi,
I think you are referring to:
http://qa.openoffice.org/files/documents/77/3247/essen2006testtool2.pdf
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"
To ease this procedure, to get through all dialogs, you may use the
VCL TestTool.
The scripts are mentioned on the page before at
'How to make Screenshots of Dialogs'
To get easy almost every dialog, run:
qa/qatesttool/writer/update/w_updt.bas
To get more dialogs, run:
qa/qatesttool/calc/update/c_updt.bas
qa/qatesttool/graphics/update/i_updt.bas
qa/qatesttool/base/update/b_updt.bas
qa/qatesttool/graphics/update/i_updt.bas
qa/qatesttool/math/update/m_updt.bas
To get still some more, run:
qa/qatesttool/framework/update/f_updt_*.bas
These scripts produce results, you have to read;
If a string is cut of, there is a colored message, telling you which one.
The 'documentation' ;-) is very short - it was in conjunction with a
presentation. So it is just an extract.
If something is unclear, please ask ...
Is there a direct link to the TCM testcase?
cheers
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
