FormProcessor: the next step

Having spent the past 8 weeks not doing any programming (and 6 of those weeks without an Internet connection) I’ve reached the stage where I *want* to do some again. I also want/need to get FormProcessor finished.

The first thing that needs doing for FormProcessor is unit tests. I have done most of the work to convert Formprocessor to handling fields with @[]@ or @[foobar]@ in their names, but I think its broken and buggy in one or two places.

“SimpleTest”:http://www.lastcraft.com/simple_test.php seems to be the library everyone talks about in PHP.

Is there anyone with experience of writing unit tests who is willing to help? I have no idea how to approach them for a script such as FormProcessor with so much HTML being generated, yet I know that they (or some other automated testing mechanism) is absolutely necessary.

2 comments ↓

#1 Harry Fuecks on 11.30.03 at 7:20 pm

The best is to read the documentation on the Simple Test website as well as that which comes with it - it really is well documented - the only thing I’d recommend is print it out and give yourself a quiet moment to go through it.

Once you get started, unit tests really aren’t that difficult. For examples of SimpleTest in use, we’ve got pretty extensive tests for WACT: sf.net/projects/wact (you’ll need to checkout the CVS anonymously or browse it online).

#2 Marcus Baker on 12.03.03 at 7:04 pm

Hi.

Anything I can do to help? I am in the process of creating some documentation on how to test web content at the moment, so any questions would be very interesting.

yours, Marcus

Leave a Comment