c16158772d
Renaming all README files for all top level modules to README.md, applying no content change at this stage to be able to track history of the files. These files should be edited to use correct Markdown syntax later. Change-Id: I542fa3f3d32072156f16eaad2211a397cc212665 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112977 Tested-by: Jenkins Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com> |
||
|---|---|---|
| .. | ||
| 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 | ||
| 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.