Vincent van Ravesteijn wrote: > On Tue, Nov 3, 2015 at 2:28 PM, Jean-Marc Lasgouttes <lasgout...@lyx.org> > wrote: >> >> Hi Vincent, >> >> What is the difference with the tests we current use (I mean the "make >> check" sort). The same but with better interface?
The overhead to add a test with the current setup is far too high. Using unit tests massively does only work if you do not need to do much more than adding your test function somewhere. > The current tests are all different executables, which is not really > optimal for speed in compilation and execution and has some overhead. > Now they all appear as different targets here and there. Using a test > framework also gives you a bunch of tools for writing tests (automatic > preparation and cleanup of objects, mocking, etc.). Then it gives you > the statistics and the ability to easily select tests you want to run, > etc. > > Maybe, more importantly, having a proper framework may ignite the > spirit of creating tests, which then might become a new habit. I hope so;-) Thank you very much for working on the tests. Regarding the test framework there is also boost::test (which would fit our needs as well). Unfortunately I have neither experience with gtest nor with QTest, so I don't know how it compares to these frameworks. Anyway, I think the most important thing is to have a working setup, so I don't care much which framework is used in the end. Georg
