History

Christian Lohmaier 0c4c84a14b makefile simplification: replace $(call gb_CustomTarget_get_workdir,foo) …by a simple/static $(gb_CustomTarget_workdir)/foo The build system has a lot of overly complicated leftovers from when it was introduced and had not only deal with split repositories but also had to coexist with another buildsystem. Along with lots of copy'n'paste along the years the makefiles became hard to grasp for newcomers with all our calls and evals. As a first step to streamline that, the macros from TargetLocations that simply prefix a static path to the argument (and similar of the same kind) are a natural pick before simplifying the rules themselves/getting rid of a bunch of eval statements. Change-Id: Ia06dbbcd5d1994755a2ff05b84f72ccbc4e3cab5 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167005 Tested-by: Jenkins Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>		2024-05-03 16:06:14 +02:00
..
com/sun/star/comp/bridge	'new Character' is deprecated in Java	2023-11-02 14:47:25 +01:00
qa
source	Drop some uses of css::uno::Sequence::getConstArray ...	2024-04-30 06:20:50 +02:00
CustomTarget_bridgetest.mk	makefile simplification: replace $(call gb_CustomTarget_get_workdir,foo)	2024-05-03 16:06:14 +02:00
CustomTarget_bridgetest_climaker.mk	makefile simplification: replace $(call gb_CustomTarget_get_workdir,foo)	2024-05-03 16:06:14 +02:00
CustomTarget_bridgetest_javamaker.mk	makefile simplification: replace $(call gb_CustomTarget_get_workdir,foo)	2024-05-03 16:06:14 +02:00
CustomTarget_uno_test.mk
InternalUnoApi_bridgetest.mk	Directly build UNOIDL .rdb files from .idl files	2013-09-19 15:50:04 +02:00
InternalUnoApi_performance.mk
IwyuFilter_testtools.yaml
Jar_testComponent.mk	makefile simplification: replace $(call gb_CustomTarget_get_workdir,foo)	2024-05-03 16:06:14 +02:00
Library_bridgetest-common.mk
Library_bridgetest.mk	Generally determine Rdb content from gb_*_set_componentfile calls	2021-12-10 08:14:24 +01:00
Library_constructors.mk	Generally determine Rdb content from gb_*_set_componentfile calls	2021-12-10 08:14:24 +01:00
Library_cppobj.mk	Generally determine Rdb content from gb_*_set_componentfile calls	2021-12-10 08:14:24 +01:00
Makefile	gbuild conversion: testtools module	2012-05-29 07:34:43 +02:00
Module_testtools.mk	Change the shared bridgetest code from static to dynamic library	2016-09-14 15:52:04 +02:00
Rdb_uno_services.mk
README.md

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.