> Unit-testing and independant modules is easy...unfortunately most of
> the modules in LyX depends on a multitude of other mudules makeing
> unit-testing very cumbersome and a lot of additional work.
>
> modules in the support dir could easily benefit form unit
> testing...but it is a lot of work to create the tests...
>
> And tests can be wrong too...
I agree with Lgb that unit testing is not the best use of efforts
right now. Unit tests are nice when you have a well structured
and well designed program, and they will help you to keep such
a thing.
However, LyX is neither well structured or well designed, so the
benefit of unit testing will not be grand. We will just learn that
a lot of code is broken, and we already know that.
Instead, it's much better to simply address each file in order,
document the header file, rename functions and variables to have
better names, in general clean it up, and try to make things better
small piece by piece.
And keep in mind that everything should be stable all along.
This, I believe, is the way to proceed with LyX.
This, I believe, is also the best way to learn the LyX source code:
By rewriting it in a better way.
Greets,
Asger
