James Carr wrote:
> Hi All,
>
> Our team has a lot of UI tests that run from fitnesse... these either
> use fixtures backed by httpUnit, HtmlUnit, or Selenium and test user
> requested functionality through the frontend (i.e. going through user
> paths and whatnot). Although this method has worked well (with a few
> small kinks), it's always a bit slow and I've always been a bit weary
> using fitnesse as a UI testing tool as it doesn't quite feel like it's
> the right tool for the job.
>
> My curiosity is how others have set up their UI testing frameworks of
> choice? Anything that works well?

How many tests do you have that treat UI objects as objects? I mean unit-level
tests that just assemble some GUI controls, activate the production code to
populate their properties, then query the properties back.

If you are not inventing a GUI from scratch, you shouldn't need to test the last
step - rendering the controls into a display.

--
Phlip
http://broadcast.oreilly.com/2008/10/testing-rails-partials.html