> But I think it can be a good way to test more different cases with less
> effort. What I test in the AjaxSubmitLink test is for example something that
> Matej and I talked about on IRC a few days ago. And that is that the onclick
> attribute ends with "return false;" which is important if you don't want "#"
> to be added to the address field in the browser. It was quite easy to write
> a test for that using the TagTester, while if I had to test that otherwise
> it was a more demanding task.
Calling WicketTestCase.executeXXX() and copying the output markup into
a file doesn't seem to be very demanding.
Two things. First of all IMHO it's not as fun to copy generated markup into files, as to go through the cases you test and *with java* specify which behaviour you expect. And don't underestimate this. If I don't laugh while coding on Wicket I wouldn't use as much time as I do ;)
Secondly I did a lot of the fixing of the failing unit tests in trunk and a lot of them were failing diff tests. Almost 99% of them (roughly) were because the attributes had changed places. But I still had to go through every little diff failure in a test to see if it was due to attribute ordering or it did have something to do with a case which really were different.
- Frank
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
