| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This required some changes to the framework:
* Init-/DeInitVCL is no longer done per individual test in BootstrapFixture, but
once per CppunitTest invocation in a new vclbootstrapprotector (similarly to
the exisiting unobootstrapprotector). CppunitTests that need VCL now need to
declare gb_CppunitTest_use_vcl.
* For things to work properly, the UNO component context needs to be disposed
from within DeInitVCL (cf. Desktop's Application::DeInit called from
DeInitVCL). The easiest solution was to introduce an
Application::setDeInitHook (where the hook is called from DeInitVCL)
specifically for vclbootstrapprotector to call.
* PythonTests don't (yet) call DeInitVCL; they still hook into
BootstrapFixture's original test_init functionality (to call InitVCL), and do
not make use of the vclbootstrapprotector.
Change-Id: I4f3a3c75db30b58c1cd49d81c51db14902ed68b2
|
|
see https://gerrit.libreoffice.org/#/c/3367/
and Change-Id: I00c96fa77d04b33a6f8c8cd3490dfcd9bdc9e84a for details
Change-Id: I199a75bc4042af20817265d5ef85b1134a96ff5a
|
|
|
|
We don't run any cppunit tests for cross-compiled platforms anyway, so no
point in compiling that. (Especially as compiling cppunit currently fails in a
--enable-werror build at least for Android thanks to -Wundef.)
Change-Id: I3139c62305ccfeddc0f67729f10e224618d2fc03
|
|
use this library for interface tests and implement the test in the
correct module by creating one test class per implementation class
The implementation class should inherit from all interface tests it
needs
This should make it more easy to write tests since we no longer need to
write the same test method multiple times
|
|
|
