1*cdf0e10cSrcweirThis test is for Windows only! 2*cdf0e10cSrcweir 3*cdf0e10cSrcweirThe cli test uses .NET assemblies: 4*cdf0e10cSrcweircli_types.dll, 5*cdf0e10cSrcweircli_basetypes.dll, 6*cdf0e10cSrcweircli_ure.dll, 7*cdf0e10cSrcweircli_cppuhelper.dll. 8*cdf0e10cSrcweir 9*cdf0e10cSrcweir 10*cdf0e10cSrcweirWhen an office is properly installed then these assemblies can be found in the 11*cdf0e10cSrcweirglobal assebly cache (GAC), for example in c:\windows\assembly. 12*cdf0e10cSrcweir 13*cdf0e10cSrcweirWhen the test is run then the assemblies are used from the GAC. That is 14*cdf0e10cSrcweirone has to make sure that one has the respective office installed. 15*cdf0e10cSrcweir 16*cdf0e10cSrcweirThe test can also be run without an installed office. Then the assemblies are used 17*cdf0e10cSrcweirwhich reside next to the executable. The testtools project copies the assemblies from 18*cdf0e10cSrcweirthe build environment into the wntmscixx\bin folder. 19*cdf0e10cSrcweir 20*cdf0e10cSrcweirHowever, if for some reason an assembly remains in the GAC than it is used no matter 21*cdf0e10cSrcweirwhat. 22*cdf0e10cSrcweir 23*cdf0e10cSrcweir 24*cdf0e10cSrcweirThe qa test simply executes the cli_bridgetest_inprocess.exe. All console output is decarded. 25*cdf0e10cSrcweirWhen the test fails one should directly run that executable. Then one may see the cause 26*cdf0e10cSrcweirof the failure in the console. 27