garvinhicking wrote:I can only speak for myself - I simply don't have the time for it; while writing unit tests in new environments is great because it helps your workflow, writing them for large existing projects can be a PITA.
Thx for your reply, I totally understand that. I tried to wrap my head around what the nl2br plugin does yesterday - no fun indeed

I have no problem with you as project lead taking care of other things.
garvinhicking wrote:Your suggestion to implement this "on the go" sounds good, but it might be hard to create relevant test cases for method changes. It could best be done on "real" methods that have algorithmic content (instead of "output/display" content, or general logic). Maybe we also just need more examples of this for others to jump aboard the wagon...
Right, I'm not even dreaming of a high coverage. Just sometimes (eg. nl2br) it makes understanding the methods under test a lot easier if there are test cases. So if anyone dives into code really deep and maybe even fixes a bug, then it would be great to have an additional unit test alongside it.
Providing more examples is a very good point. I will try to publish the plugin tests I've written so far to my repo.