[Kdenlive-devel] Adding unittests to kdenlive?

[Mads Bondo Dydensborg]

Hi all

I was wondering what the general feeling about unittests are?

In my work, I have found unittests (and test driven development, but this mail 
is not about that) to be a very valuable tool. Unittests both document the 
intentions of the code, makes it easier to add functionality without breaking 
the existing functionality and related to this, work as a poor-mans 
regression test tool.

As kdenlive is clearly very much a GUI program major parts of kdenlive can not 
be unittested. However, some parts can. Right now I would like to create a 
unit test for part of the KdenliveDoc::convertDocument() function. I am 
capable of doing this, but would like to know beforehand if it would be OK 
with all? (Especially JB, I reckon).

Also, what framework to use? I have experience with ccpunit and boost, but I 
reckon QtTestLib would be better to use for Kdenlive? 

http://developer.kde.org/documentation/tutorials/writingunittests/writingunittests.html

Comments welcome.

Regards

Mads

-- 
Mads Bondo Dydensborg   mads at dydensborg.dk   http://www.madsdydensborg.dk/

Those who have challenged the inequalities of global trade have pointed to
the fact that some of the world's richest nations once used tariff barriers
to devastating effect in building their economies. But the history of patent
protection suggests that that is not the only means by which the rich
nations have raised the drawbridge after entering the castle. When it suits
the rich countries to impose free trade, they do so. When it suits them to
impose protectionism, they argue that this is the only path to development.
But woe betide the poor nation which seeks to apply the lessons of the past.
                           - George Monbiot on Patent nonsense