On 21 Jan 2016, at 2:37 AM, David Tardon <dtardon@redhat.com> wrote:
Hi,
On Mon, Jan 18, 2016 at 12:53:07PM +1100, Chris Sherlock wrote:
I think a unit test might be helpful. They are actually quite easy to write - in fact, I wrote a
very simple one the other day.
Have a look on master at vcl/qa/cppunit/font.cxx
Note that you don't have to create a whole new CppunitTest every time.
You can add new source files to an existing one. You just have to make
sure that only one of the sources contains CPPUNIT_PLUGIN_IMPLEMENT(),
otherwise you'd get a linker error.
Speaking about excessively granular tests: would anyone protest against
an Easy Hack to merge the tests in sal module into bigger groups, e.g.,
just one test for osl, one for rtl and another one for sal? I.e.,
reduction of the number of CppunitTest makefiles from 33 to 3.
D.
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.