Hey Matus,
I just saw that you started using the constructor and the destructor
in the tubes unit test. It would be a better idea to move this into
setUp and tearDown and check there with CPPUNIT_ASSERT that all
variables are set. In contrast to the constructor and the destructor
setUp and tearDown are protected inside the cppunit framework against
thrown exceptions. In general using the constructor and destructor in
a cppunit test should only be done for the few cases where it is
really necessary and setUp and tearDown are no alternative.
Regards,
Markus
Context
- comment about using constructor and destructor in cppunit tests · Markus Mohrhard
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.