Re: [TFUI] comments on my first chapter

Testing GUI's first or last is hard. That is the core problem. You are
trying to provide approaches to developing UI code with a test first
approach. I say all approaches to test first user interface development in
one source work would be nice to have. I'm sure your reviewer is well
qualified at what he does, but I don't think a test engineer/ QA guy would
understand much about the reasons for TDD and TFUI, since it is a
developer's way of writing better code and they would not have had the
experience necessary to draw conclusions to why you need a TFUI book. If you
are struggling to grasp some concepts we TDD'ers take for granted then that
might foul you up enough trying to figure out what/why TFUI.

Cheers,

Jim Bennett
www.blix.net/Testing

From: "Phlip" <[email protected]>
> TFUIers:
>
> A reputable (and opinionated) test engineer and QA consultant provided
> this review of as much as he could stand of /TFUI/
>
> <netiquette mode="suspended" attrocity="public quote of private e-mail">
>
>    I couldn't find a description of what testing means to you, so I'm
having
>    trouble sorting out some fundamental philosophical basis for what
you're
>    writing.
>
>    I was also unable to find anything or anyone that I would consider a
>    reference to previously existing thought about testing.  Was this
>    intentional?  Is there a line of thinking about testing that you're
>    following (or challenging, or ignoring)?
>
>    I'm also having some difficulty following the line of reasoning; it
seems
>    to me disjointed.  That may be a reader issue, rather than a writer
issue.
>
> </netiquette>
>
> Okay, guys, is this him or me?
>
> (Or maybe has he read too many of my online posts?)
>
> The answer, in the tiniest nutshell possible, is:
>
> "The root problem is you must think of a test case that can force a
> new graphical situation, without writing the graphical situation
> itself first, AND without viewing the GUI to see if the situation
> works. Your new test should tell you it works. Think of easy GUIs,
> like data entry, and then think of hard GUIs, like rotating fractals,
> or heat maps."
>
> I say that in the first chapter like so many times, in various
> different ways, using both our brainwashed jargon and common industry
> jargon.
>
> About "reference to previously existing thought about testing", I list
> /Test Driven Development/ on Page 2... Sheesh...
>
> --
>   Phlip
>   http://www.greencheese.org/ZeekLand  <-- NOT a blog!!




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/