office-gobmx/testtools
Stephan Bergmann e7cf25437e Extended loplugin:ostr: Automatic rewrite O[U]StringLiteral: testtools
Change-Id: Idc0de002b7ca4e370add311f91576adaaf354764
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158243
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2023-10-20 16:13:38 +02:00
..
com/sun/star/comp/bridge
qa
source
CustomTarget_bridgetest.mk
CustomTarget_bridgetest_climaker.mk
CustomTarget_bridgetest_javamaker.mk
CustomTarget_uno_test.mk
InternalUnoApi_bridgetest.mk
InternalUnoApi_performance.mk
IwyuFilter_testtools.yaml
Jar_testComponent.mk
Library_bridgetest-common.mk
Library_bridgetest.mk
Library_constructors.mk
Library_cppobj.mk
Makefile
Module_testtools.mk
Rdb_uno_services.mk
README.md

Testing Tools

How to Check Compatibility Between Compilers

Since the interfaces used in the cpp bridgetest are not changed often one can just build the cppobj.uno.dll and the constructors.uno.dll (testtools/source/bridgetest) in an old environment and then use them in the new environment. That is the files are copied into the testtools/wntmsciXX.pro folder which corresponds to the new environment.

On Windows this test will typically fail because the tests use the cppu::getCaughtException function, which only works when all libs are build using the same runtime.

This part of the test can switched off. To do this go into the testtools/source/bridgetest folder and call

dmake compcheck=1

This will add a new compiler define (-DCOMPCHECK) and will be used in the bridgetest.cxx to switch off the code which uses the getCaughtException function. However, there is still a test which causes the test component to throw and IllegalArgumentException. This still works.

Using source / bridgetest for Stress Testing

Start a modified bridgetest_server (with the final --singleaccept argument removed from the uno executable call) or a modified bridgetest_javaserver (with the final singleaccept argument replaced with multi in the java executable call), then start a modified bridgetest_client (with a final stress argument added to the uno executable call). The client will continuously establish connections to the server which are immediately destroyed again. The test will run forever, unless an error occurs.