The decision to develop UI unit tests really comes down to how much
budget you have for your applications development.
If you do, than that is great. You can also develop some load testing
capability at the same time. Just note is time consuming / expensive
to do so.
regards Malcolm Edgar
On 6/14/07, Peter Schröder <Peter.Schroede..reenet-ag.de> wrote:
> hi kevin,
>
> i think that testing the ui is a very important part for a good quality web-application. it also helps understanding the webapp for new developers or reminding you of things that have been implemented in a sloppy way. it is poor that in most cases i dont take the time to write some tests on that...
>
> kind regards
> peter
>
> -----Ursprüngliche Nachricht-----
> Von: Kevin Menard [mailto:kmenar..ervprise.com]
> Gesendet: Mittwoch, 13. Juni 2007 20:34
> An: use..ayenne.apache.org
> Betreff: RE: Unit testing web apps
>
> > -----Original Message-----
> > From: Malcolm Edgar [mailto:malcolm.edga..mail.com]
> > Sent: Tuesday, June 12, 2007 9:47 PM
> > To: use..ayenne.apache.org
> > Subject: Re: Unit testing web apps
> >
> > I think writing unit tests for DAO/Service classes is OK, but
> > going up to the UI tier is not worth the effort. This is due
> > to the amount of change you see in UI's and the effort it
> > takes to write and maintain these tests.
>
> I have to disagree here. While they are a pain in the neck to maintain,
> our selenium tests have turned up numerous problems. Just recently we
> discovered a problem with using a shared data cache on certain objects.
> It also helps tests session-bound contexts.
>
> Since Selenium uses an XPath-like syntax for DOM navigation, you can
> write tests that generally work even after UI changes.
>
> --
> Kevin
>
This archive was generated by hypermail 2.0.0 : Thu Jun 14 2007 - 03:30:00 EDT