From e8980493f3ff1369ed7442d840cb36b36ae46cb1 Mon Sep 17 00:00:00 2001 From: Jens-Heiner Rechtien Date: Fri, 23 Sep 2005 10:47:55 +0000 Subject: INTEGRATION: CWS jl16 (1.1.2); FILE ADDED 2005/04/21 09:22:21 jl 1.1.2.2: #i47674# only test on windows 2005/04/21 09:04:28 jl 1.1.2.1: #i47674# Testing cli bridge --- testtools/qa/cli/readme.txt | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 testtools/qa/cli/readme.txt (limited to 'testtools/qa') diff --git a/testtools/qa/cli/readme.txt b/testtools/qa/cli/readme.txt new file mode 100644 index 000000000000..d0a55beae98b --- /dev/null +++ b/testtools/qa/cli/readme.txt @@ -0,0 +1,26 @@ +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. -- cgit