d1589ade91
The API doesn't actually work there yet because we don't get any event, so there's no point in exposing it there, and it makes it clear it isn't available there, avoiding future user to wonder why their tests do not behave there. Change-Id: I38dcc98ad3bc3b669df64bc1c53c91ef48a0d717 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147574 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de> |
||
|---|---|---|
| .. | ||
| qa/cppunit | ||
| signing-keys | ||
| source | ||
| user-template | ||
| CppunitTest_test_a11y.mk | ||
| 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.