On Thu, 2011-12-01 at 01:17 +0100, Bjoern Michaelsen wrote:
Hi,
On Wed, Nov 30, 2011 at 06:22:11PM -0500, Kohei Yoshida wrote:
So, this suggests that we first write test in python, then later rewrite
it in C++, or would python tests stay in python?
It wouldnt scare me if quite a few would not be promoted to C++, so I wouldnt
force people to do rewrites. One could keep the Python tests as the broad
base providing wide code coverage and rewrite to C++ whenever it appears
sensible (e.g. test is too slow in Python or test is fast and often violated
and thus should become an in-build test). After all a test that succeeds is not
really interesting, once the test fails -- or even crashes LO -- it is getting
interesting.
Ah! Now I got the whole picture.
My fear was only that, once we pick python everybody would have to write
tests in python, which, judging from your above comment, is not what you
are proposing at all.
I'm all fine with it as long as those who want to write test cases in C
++ are allowed to do so.
Cheers,
Kohei
--
Kohei Yoshida, LibreOffice hacker, Calc
Context
- Re: [Libreoffice] concept for c++ based subsequenttests (continued)
Re: [Libreoffice] concept for c++ based subsequenttests · Michael Meeks
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.