Don’t forget to write tests for your patches


As all new major releases Plone 3.2 is heavy tested by early integrators that want the new version. They report bugs and sometimes patches. Hopefully most of them are using ‘svn diff’ or ‘diff -u’ to prepare those patchesinstead of saying: « Replace the line XX by this and add that line here »…

But the one thing they never do it is to add a test to demonstrate their bugs. Then one of the maintainer have to take time to write a test around what (s)he think to be the bug. Often, the patch is just applied, Plone is growing with another untested code and the life continue.

Please help maintainers: if you are able to write a patch you should be able to write the associated test.

Les commentaires sont fermés.

%d blogueurs aiment cette page :