From: Jim Knowlton <jknowlton525@...>
Date: 2007-08-26T14:50:03+09:00
Subject: Re: Ruby access to Win Forms application

> Mock the thing that pops the screen up. You don't need to test the GUI
> itself, because you aren't going to refactor or upgrade that. (Hopefully!)
> You need tests that cover only your own logic. That logic isn't going
> anywhere if a test simply catches its outputs _before_ those outputs go into
> the real GUI.
>
> --
>   Phlip
>  http://www.oreilly.com/catalog/9780596510657/
>   "Test Driven Ajax (on Rails)"
>   assert_xpath, assert_javascript, & assert_ajax

Philip...Thanks for your thoughts...I guess my thought is that since I
am the QA guy, and am not writing the program code (I'd say we do
"moderately rapid but not agile" development), my job is just to
verify that the program works from a user perspective, not to unit-
test the code.  So far, I've been using Ruby/Watir to drive the
browser and test our admin utility (which is a web application)...and
that's worked great.  The only thing remaining is to be able to
"drive" the win32 client so I can verify it responds appropriately to
messages it gets from the server.  I guess my thought is, if I mock up
the client, how do I know the client is working (if I'm not actually
running it)?