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

[Hit send by mistake!]

We got a nice plug here:

http://dotnetjunkies.com/WebLog/exortech/

"As each screen class extends from JPanel, the reveal() method simply
inserts the panel into a JDialog and pops it up."

The number one FAQ about reveal() is "but that means you don't test
the GUI you just look at it!"

Our anonymous blogger (I can't find his name) immediately reports:

"The developer just needs to remember to remove the reveal method call
before committing their changes."

That reinforces reveal() is temporary. The next step is to turn it off
automatically at commit time. The goal is to remove all reasons not to
test, then remove all reasons not to commit.

Because reveal() is temporary, and it leads to automated tests that
nail down the important GUI behaviors, the very next paragraph reveals
its effect on the process:

"One additional benefit of this approach is that it drastically
reduced our code-and-verify cycle.  Previously, any changes to the
client required manual verification; given the complexity of the
application, it was quite time-consuming to navigate to the necessary
screen to validate the changes.  And of course, now the desired
functionality is captured in automated tests, protecting us from
regression."

Props!

(And I kind'a wish I could get a chance to actually do these techniques myself!)

-- 
  Phlip
  http://www.c2.com/cgi/wiki?ZeekLand


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/