I just did something that's been on my to-do list for a looong time. I hacked on JspTest a bit to tick off some age old todo's:
- JspTest now has basic support for mocking tag libraries
- I got rid of the kind of nasty dependencies to a gazillion .jar files (by getting rid of HttpUnit)
- I converted the Ant-based build script into Maven
- I put together a public release
There's a lot to do, still, such as documentation, JSP 2.0 support, better facilities for mocking stuff, better support for HTML-based assertions, etc. For example, you'll have to figure out from the (hopefully intuitive) API how to use the damn thing and you'll have to implement pretty much all assertions for the rendered content yourself. It's getting better all the time, though!
One of the big things I did that wasn't on the above list is the public release. You no longer need to check out from Subversion but rather just download a zip file. The only release available through Sourceforge is 0.6, however, and the above improvements were made to 0.7 for which you'll have to wait a bit longer. Those improvements did not change the relevant APIs, though, so there's no reason not to get a head start with 0.6 while you're waiting for 0.7.
Having a public release is an improvement in itself but giving JspTest a try is also getting easier now that the project is using Maven. That is, once the little squirrels behind the public Maven repositories get the POMs and JARs uploaded, you can simply add JspTest as a dependency into your own pom.xml and start writing tests!
Oh, and voting for the ticket would help in getting the squirrels moving!