2dde21ea74
Accessibility tests will require testing the normal UI, so will need not alter the search path for definitions. It will however benefit from other environmental overrides (locale, fonts, etc.). The solution here splits out to a separate registry the piece of configuration that alter the UI, so users can select the features set they need. The default gb_CppunitTest_use_configuration is updated to keep working the same as before, using both layers. gb_CppunitTest_use_unittest_configuration is replaced by specific ones for each configuration layer, and the two direct call sites removed as they were redundant anyway (gb_CppunitTest_use_unittest_configuration is only a subset of gb_CppunitTest_use_configuration). New macros are gb_CppunitTest_use_common_configuration for the common layer and gb_CppunitTest_use_user_ui_configuration for the UI one. Change-Id: I75f82092079752b4e173e48ab463636e7b7515b6 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/136997 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com> |
||
|---|---|---|
| .. | ||
| qa/cppunit | ||
| signing-keys | ||
| source | ||
| user-template | ||
| CppunitTest_test_xpath.mk | ||
| IwyuFilter_test.yaml | ||
| Library_subsequenttest.mk | ||
| Library_test.mk | ||
| Library_test_setupvcl.mk | ||
| Library_vclbootstrapprotector.mk | ||
| Makefile | ||
| Module_test.mk | ||
| Package_unittest.mk | ||
| README.md | ||
| README.vars | ||
Test Harness Code for C++ Unit Testing
Many of these tests are run during the build process. In that case on
unix, if a test fails follow the error messages to debug it under gdb.