Re: Re: Comparing documents for functionality tests + Build Problems

Lars Langhans schrieb:
>
> Hi Steffen,
>
> as Stephan Bergmann already mentioned, there exists a real new module
> testgraphical, which is not completely ready yet, but at least usable.
>
> Build the module 'qadevOOo' there you will find the 'OOoRunnerLight.jar'.
>   
I'm not able to build the module 'qadevOOo' at the moment. The dependent 
jar's are not created yet. I guess it's because I didn't get a full 
build to work up until now.

build --from qadevOOo --prepare

runs through, but

----------------
build --from qadevOOo

qadevOOo_runner_build:
Compiling 195 source files to 
/*/**/**/**/working_OOO/qadevOOo/unxlngx6.pro/class
/*/**/**/**/working_OOO/qadevOOo/runner/convwatch/OfficePrint.java:121: 
incompatible types
found   : java.lang.Object
required: com.sun.star.frame.XModel
            XModel xModel =  UnoRuntime.queryInterface( XModel.class, 
_aDoc);
                                                      ^
/*/**/**/**/working_OOO/qadevOOo/runner/convwatch/OfficePrint.java:164: 
incompatible types
found   : java.lang.Object
required: com.sun.star.frame.XDesktop
                XDesktop aDesktop = 
UnoRuntime.queryInterface(XDesktop.class, oDsk);
                                                             ^
/*/**/**/**/working_OOO/qadevOOo/runner/convwatch/OfficePrint.java:215: 
incompatible types
found   : java.lang.Object
required: com.sun.star.frame.XComponentLoader
                    XComponentLoader aCompLoader = 
UnoRuntime.queryInterface( XComponentLoader.class, aDesktop);
             
                                                               ^
...
----------------

There are 52 similar errors following. That's why I wanted to make a 
build --all first, but that is giving me trouble as written in the last 
mail.
With build --all i get problems in module 'sal'

----------------
...
Entering /*/**/**/**/working_OOO/sal/util

Compiling: sal/unxlngx6.pro/misc/uno_sal_version.c
Compiling: sal/unxlngx6.pro/misc/salalloc_malloc_version.c
Making:    sal.lib
Making:    asal.lib
Making:    libsallx.a
ar: creating ../unxlngx6.pro/lib/libsallx.a
echo '#ifndef _SAL_UDKVERSION_H_'           >  
../unxlngx6.pro/inc/udkversion.h
echo '#define _SAL_UDKVERSION_H_'           >> 
../unxlngx6.pro/inc/udkversion.h
echo ''                                     >> 
../unxlngx6.pro/inc/udkversion.h
echo '#define SAL_UDK_MAJOR "3"' >> ../unxlngx6.pro/inc/udkversion.h
echo '#define SAL_UDK_MINOR "2"' >> ../unxlngx6.pro/inc/udkversion.h
echo '#define SAL_UDK_MICRO "7"' >> ../unxlngx6.pro/inc/udkversion.h
echo ''                                     >> 
../unxlngx6.pro/inc/udkversion.h
echo '#endif'                               >> 
../unxlngx6.pro/inc/udkversion.h
Making:    libuno_sal.so.3
Making:    libsalalloc_malloc.so.3
: WARNING: ../unxlngx6.pro/lib/check_libsalalloc_malloc.so.3: undefined 
symbol: GetVersionInfo
testshl ../unxlngx6.pro/lib/libuno_sal.so.3 sce/uno_sal.sce -msg -skip
dmake:  Error executing 'testshl': No such file or directory
dmake:  Error code -1, while making 'runtest_uno_sal'

1 module(s):
        sal
need(s) to be rebuilt
...
----------------

Don't know how to solve this one :/ .

> And the Convwatch documentation is outdated, sorry.
>   
No problem, I truly understand the documentation problems of changing 
content. My documentation here at work isn't updated frequently either ;) .
> testgraphical:
> --------------
>
> You need some other software to work with this graphical compare.
> I've create a checker for this so just do the follows.
>
> # cd testgraphical/prechecks
> # dmake verbose=1 SHOW=1
>
> - Ghostscript is need
> - Imagemagick is need
> - Java 6 is need
>   
Precheck accomplished.
> Now start a connectable office, you don't know how?
>
> # cd ../source
> # dmake
>
> This should hopefully fail with a java.lang.NullPointerException. But 2
> lines before the error stack trace it told you, how to run a connectable
> office.
>   
Can't try this one, because I'm not able to build module 'sal' :/ But I 
guess this task should be no problem after the build has gone through.
> How can you use it for your own:
> --------------------------------
>
> The documents came from 'demo' pool:
> testgraphical/document-pool/<POOL>    (here <POOL>:=demo)
>
> You can copy your test documents to testgraphical/document-pool/demo or
> create a new own <POOL>. (Limitations: Subdirs in <POOL> are not
> supported yet!)
>
> The reference document result(!) (how it should look like) (pdf or
> postscript) came from:
> testgraphical/references/unxlngi/<POOL>
>
> Here you have to copy your pdf export of your test documents with a
> office which you made as your 'reference'.
>
> IMPORTANT: Due to font differences there exists sub directories for
> unxlngi (linux x86), windows (wntmsci), Solaris Intel (unxsoli).
>
> If you use the 'demo' pool, you could use 'dmake demo' for test runs. If
> you like the extra java helper with 3 views you have to start with
> 'dmake demo SHOW=1'.
>
> Tips:
> * If you use your own pool, just create a new line in the makefile.mk
> like the 'demo:' line.
> * Use pdf export.
>   
Sounds doable.
> Please report problems.
>   
I did :) . Even if it's rather general build problems than explicit 
problems with the testgraphical module.
> This tool should also work within windows and solaris intel, but as I
> mentioned before, not completely ready yet.
>   
Most of our tests here at work are executed under linux anyway. So Linux 
support is absolultey great.

Regards,
Steffen