Thanks, Gregor, Yes it is a great help.
Is it possible to download the sources of
testtool somewhere ? Or to have them
communicated to the French team ?
Best regards
Hélène
Gregor Hartmann a écrit le 07/12/2005 12:54 :
Hi,
AFAIK there is no such document so far.
The Documentation has been the sourcecode.
But let me write down some information here:
very line contains 6 columns separated by semicolons
LogType;Filename;Line;ColStart;ColEnd;Message
LogType is a number with the following meaning:
0 = LOG_RUN
1 = LOG_TEST_CASE
2 = LOG_ERROR
3 = LOG_CALL_STACK
4 = LOG_MESSAGE
5 = LOG_WARNING
6 = LOG_ASSERTION
7 = LOG_QA_ERROR
8 = LOG_ASSERTION_STACK
Filenames are prepended by one or two characters which give it a special
meaning
"~" The filename is relative to the "Base directory" given in the
settings dialog
"~-" The filename is outside of the "Base directory" and has to be left
untouched.
The line contains the line number in the file
ColStart and ColEnd might be off by some spaces or collons if several
commands are combined on one line. At the line end the ColEnd might be
65767 (0xffff).
The Message is unreadable because it only contains the resource number of
the message to display.
The advantage of this is to see the resultfile in the language of the UI.
Maybe it would also be a good idea to have a look into the following
commands, which could help you performing your task inside the basic scripts.
GetErrorCount
GetWarningCount
GetQAErrorCount
GetUseFileWarningCount
The following return a string array (in readable text, not as in the
resultfile)
GetErrorList
GetWarningList
GetQAErrorList
GetUseFileWarningList
Hope to help
Gregor
Ursprüngliche Nachricht <<<<<<<<<<<<<<<<<<
Am 06.12.05, 14:54:23, schrieb Laurent Godard <[EMAIL PROTECTED]> zum
Thema [qa-dev] [testTools]result file structure:
Hi
Testtool has been running now for 26 hours on a win box (still playing -
good guy). I end wit a lot of .res files i'll have to check
As it is text files, i plan to pre-analyze them by a script (who said a
macro ;) ). Is there any document describing the file structure so that
i can parse thes files and search for errors ?
Thanks in advance
Laurent
--
Laurent Godard <[EMAIL PROTECTED]> - Ingénierie OpenOffice.org
Indesko >> http://www.indesko.com
Nuxeo CPS >> http://www.nuxeo.com - http://www.cps-project.org
Livre "Programmation OpenOffice.org", Eyrolles 2004
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
