(sending reply to list as well, accidental private reply) Yes! We want loads of unit tests. We do this for Taglib# and it has proven massively useful. There are currently only two unit tests because I just removed all the old and broken ones. So go ahead and add tons, they will be maintained. Also, patches that make it easier to test things + tests will certainly be accepted. Go for it!
On Mon, 2010-06-07 at 19:00 +0200, Daniel Köb wrote: > Hi, > > For some code changes I'm planning to make I would like to write some > unit tests first. It's always nice to know that you didn't break > anything unexpectedly in some tricky function... > The HACKING file states in a single paragraph that NUnit is used for > unit testing and explains a little bit how such tests should be > implemented. Unfortunately, this paragraph is rather outdated (2006) and > it seems to be wrong at least for some parts. > > So my first question is: Is anybody writing unit tests when hacking f-spot? > > Furthermore, I managed to build and run the existing tests (2, is this > it?!?). I also managed to write, build, and run my own tests with some > problems I had to work around. > Before I'm going into more detail about these problems and asking > further questions I would like to know if f-spot should have unit tests > at all (I'd say yes) and if they would be used and maintained by others > as well. > > Regards, > Daniel > _______________________________________________ > f-spot-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/f-spot-list > _______________________________________________ f-spot-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/f-spot-list
