From: Kevin <ke...@dr...> - 2005-12-05 14:30:44
|
Andrew Turner (nilspace) wrote: >Only concerned that we haven't done it yet and more often. ;) > >I think this is an excellent idea. It had crossed my mind, but got >pushed back. Thanks for putting this together. I assume we can write >tests for all the major functionality: adding, removing, viewing >feeds, generated OPML, generated RSS (future feature)? > > FoFr is a small project, but it can still benefit from unit testing. It makes heavy use of functions to organize the backend code.(see also: "a good thing") This type of code organization makes it easier to test. I figured each fof function will have it's own test case class. I've already created one for fof_content_sanitize(). Question: Should the tests be included in code releases? I don't see the benefit in that. I figure they will just live in the CVS repository for developers to use. >I haven't seen SimpleTest before, I'll make sure to check it out. > > The two choices are SimpleTest and PHPUnit. I've only ever used SimpleTest. I gave the list a heads up in case someone wanted to pipe up with compelling reasons to use PHPUnit instead. If no one has objections, I'll commit what I have. |