Posted: Fri Aug 18, 2006 9:13 pm
So... is anyone using it? Comments? Gripes? Anyone discover the latent configuration system that as of right now is totally undocumented?
A community of PHP developers offering assistance, advice, discussion, and friendship.
http://forums.devnetwork.net/
Last time I checked phpDoc didn't do that. There was a standalone application, phpxref thoughwhich I don't think phpDoc does but I might be mistaken
Component wise, yes. Check out the tests/ folder. Or check this out. (edit: Rawr, the unit tests are broken. How the heck did that happen? Apache's refusing to boot too on my computer... will investigate).AC has this been thoroughly unit tested?
That's an interesting new feature, and we'd probably want that. However, regarding the overarching scheme of things, HTML in and HTML out, I think we're better off having more informal smoketests to ensure that the output is sane.HTML isn't easy to test in any flexible way. If you could run it through HTMLPurifier and have it tell you how many purifications it made that would be a start. Being about to browse the HTML like a document tree and check values inside would be good too, I guess I could use XMLDom for that though.
Well, it seems now phpDoc does. I'll check phpxref too. However, my primary complaint with phpDoc still stands: it takes too long!Last time I checked phpDoc didn't do that. There was a standalone application, phpxref though
What is a smoketest?I think we're better off having more informal smoketests to ensure that the output is sane.
Visual check test performed by a human during tests.ole wrote:What is a smoketest?