[scribus-dev] unit test

Craig Bradney cbradney at scribus.info
Tue Jun 25 20:03:59 UTC 2013

On 25/06/2013, at 21:47, Brunet Pierrick <pierrick.brunet at telecom-bretagne.eu> wrote:

> Hi everyone,
> As some of you may know, I plan to work on including unittest in Scribus. Something done by Avox already exist but it doesn't work anymore. The real question is : is it a good idea to work on it?
> Pros:
> -with unit-test, coredev will not need to test patch and review will be easier (so patch will be merged faster)
> -No regression. Sometime it looks like we solve a bug, then another, then we solve the first bug again...
> -More efficient to detect bug than assert in code
> Cons:
> -More code to maintain (even if as there are no regression and no functionnality are deleted, we should not change these codes)
> -Test have to be add when we add functionnality
> -Test have to be use before commiting in the holly master branch
> I am waiting for you comment before doing any work. If most of you think it is useless, we may delete tests folder in scribus, otherwise, I am ready to work on it.
> Good evening,
> Chelen
> _______________________________________________
> scribus-dev mailing list
> scribus-dev at lists.scribus.net
> http://lists.scribus.net/mailman/listinfo/scribus-dev

I think it's a great idea, although there's other stuff that will help get 1.5.0 released faster that needs doing (and unit testing probably won't help get 1.5.0 released faster). In any case, unit testing is needed so I'd support the effort.


More information about the scribus-dev mailing list