| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
Needs a deleted canvastools method, move code into more idiomatic
vcl/qa place, adapt to new unit test framework.
Change-Id: Iddb9c2249673b4d580e46a1d72029be0a8c4d9ba
|
|
Change-Id: I2528cfd2a4d520d4400ae72a53c085484e0f86aa
|
|
Change-Id: I11a1845350e3404f348be1321571b19d816426a3
|
