Re: Re: PEAR Mail_Mime status?

>>> The status is well ... stall ... Sean does not want to do any changes >>> unless there are some more unit tests but he lacks the time to write >> them, >>> so if you want to contribute some tests then we'd appreciate that! :) >> So, which Tests have to be written? > > > Well just what ever comes to mind I'd guess, would be wise to take each > function by it self and write test case for various combination of options > and input data, but Sean will know for sure what he'd like to see first for > example :) Sorry for the late reply. Here's the deal: I have very limited time to devote to PEAR. I recognize that Mail_Mime is a very important package, and it's also an old package. There are a number of pending patches sitting in the bug tracker. When I took over development of the package (Cipri is also still somewhat active), I was zealous, but ran into several brick walls related to internationalization. As it stands, I'm very scared of breaking the package. There are VERY few tests (I wrote the ones in CVS). The package has several years of history, and I'd guess that there are thousands (or more?) applications out there actively using Mail_Mime. I'm not willing to break these. So, if you want to help, by all means, PLEASE, PLEASE write whatever tests you can. I'll make it a priority to get them into CVS. phpt tests, please. If you're wondering what to test, it's simple: everything. (-: Once we have decent coverage, I'll be much more likely to invest time in the package. If nothing else, then at least to test the patches that have been building up in the bugtracker for the past several months. S