office-gobmx/testtools/qa/cli
Rüdiger Timm a940d7dab2 INTEGRATION: CWS changefileheader (1.4.36); FILE MERGED
2008/03/31 07:26:28 rt 1.4.36.1: #i87441# Change license header to LPGL v3.
2008-04-11 11:23:25 +00:00
..
CLITest.java INTEGRATION: CWS changefileheader (1.3.84); FILE MERGED 2008-04-11 11:23:06 +00:00
makefile.mk INTEGRATION: CWS changefileheader (1.4.36); FILE MERGED 2008-04-11 11:23:25 +00:00
readme.txt

This test is for Windows only!

The cli test uses .NET assemblies: 
cli_types.dll, 
cli_basetypes.dll, 
cli_ure.dll, 
cli_cppuhelper.dll.


When an office is properly installed then these assemblies can be found in the 
global assebly cache (GAC), for example in c:\windows\assembly.

When the test is run then the assemblies are used from the GAC. That is 
one has to make sure that one has the respective office installed.

The test can also be run without an installed office. Then the assemblies are used 
which reside next to the executable. The testtools project copies the assemblies from
the build environment into the wntmscixx\bin folder.

However, if for some reason an assembly remains in the GAC than it is used no matter 
what.


The qa test simply executes the cli_bridgetest_inprocess.exe. All console output is decarded.
When the test fails one should directly run that executable. Then one may see the cause 
of the failure in the console.