Date: prev next · Thread: first prev next last
2017 Archives by date, by thread · List index


Hi all,

I wonder what the reason of running some of the unit tests by calling
simple make on a module (e.g. make sd). I used to use simple make while
doing the intensive hacking of the code, when I don't need to run unit
tests at all. After I finished with the codewriting, I can run the unit
tests with make check or a top level make. I guess there is some additional
option with which I can avoid unit tests, but I would not waste my time
with typing.
So I wonder whether there is any good reason for having this unit tests run
by make. Why don't we run tests only by make check? Nowdays most of the
patches are pushed via gerrit, so we don't need to worry about that the
commiter don't run the unit tests before pushing to the branch. So I think
it might be good to remove this type of unit tests and run these tests as
slow check targets. At least a config option would be usefull, which can do
that.

Any thoughts about this?

Best Regards,
Tamás

Context


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.