Re: [TFUI] Re: reveal() leads to short cycle times?

Tony Nassar wrote:


>I think I missed something. Your reveal() is like Show() in .NET, right?
> Host the control in a dialog (possibly as part of a SetUp method), then
> bring it up and exercise it.

The window comes up in the state where the test puts it. You can call 
reveal() anywhere in a test, and it will block at that point.

Ideally, when you close the window the tests resume (and the window's object 
persists in memory until de-rezzed).

None-ideally, you just look at or drive the window, then whack the test run, 
comment out the reveal(), and test again.

The point is to ensure that a clever test has not lead you astray. Some GUIs 
cannot accurately Get some of their  Set conditions, and vice-versa, so 
frequent inspections discover these blind spots. When discovered, you 
upgrade the test to make it more accurate.

When future test cases re-use this test case's techniques, you can start 
coding GUIs heads-down, and add entire features without displaying them.

-- 
  Phlip
  http://www.greencheese.org/ZeekLand  <-- NOT a blog!!! 



------------------------ Yahoo! Groups Sponsor --------------------~--> 
Most low income households are not online. Help bridge the digital divide today!
http://us.click.yahoo.com/cd_AJB/QnQLAA/TtwFAA/nhFolB/TM
--------------------------------------------------------------------~-> 

To unsubscribe, email:
TestFirstUserInterfaces-unsubscribe-hHKSG33TihhbjbujkaE4pw@public.gmane.org
 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/TestFirstUserInterfaces/

<*> To unsubscribe from this group, send an email to:
    TestFirstUserInterfaces-unsubscribe-hHKSG33TihhbjbujkaE4pw@public.gmane.org

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/