I've found HTMLUnit, in the past to be utterly awful. At least with our web app (lots of ajax) HTMLUnit struggled and I ran into a lot of bugs.
On Fri, Nov 4, 2011 at 9:18 AM, Kalle Korhonen <kalle.o.korho...@gmail.com>wrote: > Your mileage may vary but for my perspective, see > > http://docs.codehaus.org/display/TYNAMO/2010/07/30/Full+web+integration+testing+in+a+single+JVM > . > For service level tests, I tend to use Mockito a lot. > > Kalle > > > On Fri, Nov 4, 2011 at 7:01 AM, Markus Johnston <tapes...@garstasio.com> > wrote: > > We have been struggling (in my opinion) with a strategy to properly and > > completely test our web application (developed using Tapestry). We have > > some unit tests, but they are all centered on the code closer to the > model. > > We have very few, if any, view and controller tests. We made some > > attempts in the past to write selenium tests, but for whatever reason, > that > > did not catch on. We have also attempted to use WebDriver along with > Geb, > > but continued to run into reliability issues with WebDriver and were > > frustrated with the inability of the WebDriver developers to settle on an > > API. Geb has some nice features to it, though. > > > > We very much would like to start writing view and controller tests. I > was > > wondering what other Tapestry users are doing, as far as testing is > > concerned. What problems have you run into? What tools or approaches > have > > you found that work especially well? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
