Op 29-4-2013 9:30, Elmar Hinz schreef:
Hello,
I understand why you think it is rather hard to do unit testing for lyx.
There are class files with up to 6403 lines of code.
src/Buffer.cpp has 4803 lines and many files depend on that.
So, what exactly is the problem with large files ?
What does
Hello,
I understand why you think it is rather hard to do unit testing for lyx.
There are class files with up to 6403 lines of code.
src/Buffer.cpp has 4803 lines and many files depend on that.
After all setting up a wall of unit test is the prerequest for
refactoring to more maintainable code an
Hello,
Scott Kostyshak was interested in unit tests.
For me working with unit tests is the most simple way to fix a bug,
as I only need to focus on the iussue, without running the rest of
the system.
As a proof of concept I testet the googletest framework today.
It is controlled by cmake. I
Peter Kümmel wrote:
> José Matos wrote:
>> On Sunday 15 April 2007 10:47:25 am Peter Kümmel wrote:
>>> Any comments?
>> Code is welcome. :-)
>
> I will have a closer look at the qt framework, so we don't have to add
> an additional dependency.
and at this project:
http://sourceforge.net/projects
José Matos wrote:
> On Sunday 15 April 2007 10:47:25 am Peter Kümmel wrote:
>> Any comments?
>
> Code is welcome. :-)
I will have a closer look at the qt framework, so we don't have to add
an additional dependency.
>
> I had played with some of those ideas for lyx2lyx and I like the outcome. :-
On Sunday 15 April 2007 10:47:25 am Peter Kümmel wrote:
> Any comments?
Code is welcome. :-)
I had played with some of those ideas for lyx2lyx and I like the outcome. :-)
We have in the repository lyx files to test for upgrade regressions that could
be better explored with automatic tests.
So
Peter Kümmel wrote:
> - Qt, http://doc.trolltech.com/4.2/qtestlib-manual.html
> - CppUnit, http://cppunit.sourceforge.net/cgi-bin/moin.cgi
Is there a free tool for testing the GUI?
Something like the commercial Squish:
http://www.froglogic.com/pg?id=Products&category=squish&sub=editions&subsub=qt
Reading the thread about beta 2 I had
the idea that we should start implementing
unit tests.
Here are some arguments:
* Currently it is only possible to test if a
change has broken something, by using the
final application. But this is not enough,
because there are so many cases which must
be
