strepsirrhini/office-gobmx
9
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
office-gobmx/testtools
History
Arnaud VERSINI 555f433318 use std::this_thread::sleep_for instead of osl equivalent 
Change-Id: I5b4edc5417e5bb5e082688df616e1d5735717d92
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142357
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2023-01-09 08:37:35 +00:00
..
com/sun/star/comp/bridge
qa
source use std::this_thread::sleep_for instead of osl equivalent 2023-01-09 08:37:35 +00:00
CustomTarget_bridgetest.mk Move manual bridgetest_inprocess_java to automatic CustomTarget_uno_test check 2023-01-03 11:57:27 +00:00
CustomTarget_bridgetest_climaker.mk
CustomTarget_bridgetest_javamaker.mk GBUILD_TRACE, support for finding out where the build time is spent 2020-02-16 14:49:45 +01:00
CustomTarget_uno_test.mk Missing test dependencies 2023-01-04 07:54:07 +00:00
InternalUnoApi_bridgetest.mk
InternalUnoApi_performance.mk
IwyuFilter_testtools.yaml Recheck modules t* with IWYU 2022-04-02 23:32:08 +02:00
Jar_testComponent.mk Generally determine Rdb content from gb_*_set_componentfile calls 2021-12-10 08:14:24 +01: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
Module_testtools.mk
Rdb_uno_services.mk Generally determine Rdb content from gb_*_set_componentfile calls 2021-12-10 08:14:24 +01:00
README.md Updated README.md files to represent current code / use Markdown format 2021-04-07 17:47:16 +02:00

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.