Two tools to look into result files *.res of qatesttool

For those who prefer command line tools to GUI ones:

Here are two Perl script tools that help testers look into
result files (*.res) of qatesttool.

 1. make_summary.pl
    summarizes the number of errors and warnings.

 2. translate_res_file.pl
    translates a res file(s) into human readable format.

http://www.openoffice.org/issues/show_bug.cgi?id=70775

I wish those tools help people and someone wants to upgrade
them.

Regards,
Tora

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org

Hi Tora,

tora schrieb:
> For those who prefer command line tools to GUI ones:
>
> Here are two Perl script tools that help testers look
into
> result files (*.res) of qatesttool.
>
>  1. make_summary.pl
>     summarizes the number of errors and warnings.
>
>  2. translate_res_file.pl
>     translates a res file(s) into human readable
format.
>
> http://www.openoffice.org/issues/show_bug.cgi?id=70775
>
> I wish those tools help people and someone wants to
upgrade them.
>   

thanks for the scripts. I just used them to analyze my test
run on 
linux. Now I do not to check every result file manually 

and my results are
Filename                      Errors    Warnings  
Warnings_during_initialization
============================  ======    ========  
==============================
b_updt.res                         0           0           0
ch_updt.res                        0           0           0
closeoffice.res                    0           0           0
c_updt.res                         0           0           0
d_updt.res                         0           0           0
first.res                          1           0           0
f_updt_help.res                    0           0           0
f_updt_pkgmgr.res                  0           0           0
f_updt_spadmin.res                 0           0           0
f_updt_templates.res               0           4           0
f_updt_windowfuncs.res             0           0           0
gallery.res                        1           3           0
i_updt_1.res                       0           0           0
i_updt_2.res                       0           0           0
ma_updt.res                        0           0           0
m_updt.res                         0           0           0
oasis_graphics_update.res          0           0           0
topten.res                         0           0           0
w_updt.res                         0           0           0
ww_updt.res                        0           0           0
xforms_updt.res                    0           0           0
============================================================
====================
Total 21 files                     2           7           0

the error in first.res is my own fault ... I need to check
the error in 
gallery.res.

André

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org

Andre Schnabel wrote:

>
>
> and my results are
> Filename                      Errors    Warnings  
> Warnings_during_initialization
> ============================  ======    ========  
> ==============================
>
> gallery.res                        1           3       
   0
>  
>
> the error in first.res is my own fault ... I need to
check the error 
> in gallery.res.
>
might be related to:
http://qa.openoffice.org/issues/show_bug.cgi?id=27735

the test isn't adjusted to OpenOffice.org;
It expects StarOffice....

cheers
Thorsten

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org

Thorsten Bosbach wrote:
>> Filename                      Errors    Warnings 
Warnings_during_initialization
>> ============================  ======    ======== 
==============================
>> gallery.res                        1           3   
       0

> might be related to:
> http://qa.openoffice.org/issues/show_bug.cgi?id=27735

And, it would be easy to know the error message by simply
doing grep.

  perl translate_res_file.pl gallery.res | grep ERROR
  ERROR: Gallerys : Entry number 21 is too large in Select.
Max. allowed is 6

Ciao,
Tora

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org

Hi,

Tora schrieb:
> Thorsten Bosbach wrote:
>>> Filename                      Errors   
Warnings  
>>> Warnings_during_initialization
>>> ============================  ======   
========  
>>> ==============================
>>> gallery.res                        1          
3           0
>
>> might be related to:
>> http://qa.openoffice.org/issues/show_bug.cgi?id=27735

yes. that is the problem. (I guessed so already)

>
> And, it would be easy to know the error message by
simply doing grep.
>
>  perl translate_res_file.pl gallery.res | grep ERROR
>  ERROR: Gallerys : Entry number 21 is too large in
Select. Max. 
> allowed is 6

Correct .. but at the moment I still rather use testtool to
analyze 
errors, as I can see the information in context
(doubleklcick onb error 
line will bring be to the corresponding code lines in the
testscript).

But using your tools, I only need to anlyce one (the failed)
file .. not 
all 21 

André

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org

Andre Schnabel wrote:
> Correct .. but at the moment I still rather use
testtool to analyze 
> errors, as I can see the information in context
(doubleklcick onb error 
> line will bring be to the corresponding code lines in
the testscript).

Yes, you are right. The testtool is well made.

For emacs accustomed guys like me, the following magical
spell
within emacs will take them to the corresponding code.

  Esc x compile RET
  perl translate_res_file.pl --with-file gallery.res RET
  Ctrl-s error:
  Ctrl-c Ctrl-c

Why i prefer to use such command line tools is that the
machine where
the testtool is running is located remotely through the
Internet.
The automation test takes hours. During the test I can go to
other place.

> But using your tools, I only need to anlyce one (the
failed) file .. not 
> all 21 

Good.

Ciao,
Tora

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org

Tora wrote:
> Andre Schnabel wrote:
>> Correct .. but at the moment I still rather use
testtool to analyze
>> errors, as I can see the information in context
(doubleklcick onb
>> error line will bring be to the corresponding code
lines in the
>> testscript).
>
> Yes, you are right. The testtool is well made.
>
> For emacs accustomed guys like me, the following
magical spell
> within emacs will take them to the corresponding code.
>
>  Esc x compile RET
>  perl translate_res_file.pl --with-file gallery.res RET
>  Ctrl-s error:
>  Ctrl-c Ctrl-c
>
> Why i prefer to use such command line tools is that the
machine where
> the testtool is running is located remotely through the
Internet.
> The automation test takes hours. During the test I can
go to other place.
>
>> But using your tools, I only need to anlyce one
(the failed) file ..
>> not all 21 
>
> Good.
Thank you for these tools. I am EMACS 'stupid' but may
decide to become
smart.  I am working my way through BASE because of the high
number of
false errors that are reported due to the imporper use of
functions to
open and close windows.  At least that is the situation on
the Mac OS X
platforms.  I will work through the issues and feedback
corrected files.

James McKenzie


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org