Alan Cyment wrote:

> Shall automated acceptance tests use the GUI the app provides? Selenium
> takes this approach whereas I reckon FIT does not...I'm currently
> developing
> an ad-hoc engine for my app (Win32 app with inputs more complex than those
> that FIT can handle) and I'm not sure which path I should take: tests that
> make use of the GUI are more realistic, but on the other hand are a lot
> slower and fragile.
>
> Thoughts on this point?

Treat the GUI as just another library, and _start_ with fearless unit tests
on it. If by Win32 you mean its widgets layer - buttons, edit fields, and
other ready-made controls - you can generally test those by populating them
in production code, and querying their states back in test code. This
requires taking control of the event loop, and forcing virtual updates
without displaying a window (or by quickly displaying it), yet the result is
much more efficient than driving the GUI thru its input system.

--
Phlip
http://www.oreilly.com/catalog/9780596510657/
"Test Driven Ajax (on Rails)"
assert_xpath, assert_javascript, & assert_ajax