[TFUI] Re: [TDD] CppUnitLite Documentation, etc.

Anderson, Kelly wrote:

> I thought your framework was called RecursiveDescentParser... I
> understand the name NanoCPP. Is that yours? I thought you said yours was
> "Based on" NanoCPP, which is why I asked about the name
> RecursiveDescentParser... which doesn't sound like much of a name for a
> testing framework ;-)

Uh, belting out a bug-free math evaluator in an afternoon is mythic.
It's like going from COBOL to Lisp on punched cards. But the test
runner is NanoCppUnit, which is both nebulous (I have several
instances of it floating around), and a sucky name. It's not about the
Unit.

> I do wonder how it would work in the context of regression testing on a
> build machine... but perhaps that's not your design goal.

The big division here

> I still use F5, not Ctrl+Shift+F5 anyways.... I use the caveman keyboard
> mapping...  :-)

Nonono - I will explain again.

My NanoCppUnit runs when you tap <F5> in Visual Studio Classic. That's
because it's JUST YOUR PROGRAM. It's not a magic strap-on DLL thing.

(But VC++ insists on asking for incredibly stupid permission to
compile, so that's two keystrokes. Some folks add the test run as the
last step in the compile, so that's back to one keystroke, but hard to
debug.)

Under a Magic Newfangled editor like Eclipse, NetBeans, etc, you have
a module supporting JUnit as a strap-on tool. So the tests are NOT
JUST YOUR PROGRAM. Then you get different keystrokes to run your
program or run the tests.

In VC++, I typically configure the Release build of an application to
run without tests. (And, gee, maybe you never need to debug unless you
are also testing. If you occassionally do, comment-out the test run in
main() and debug away...)

So these Magic Newfangled editors with built-in support for testing
typically don't put the most important action
(save+compile+test+display faults) under one keystroke. Because they
put other commands into the un-shifted Function keys first, when they
got around to *Unit they are into the shifted keys.

It's not just about the keystrokes. We all here use muscle memory to
get around all kinds of situations, including things like deleting the
ads when we reply to a Yahoo Groups mailing list. It's about the
general philosophy of editors that enable Flow instead of inhibit it.

This is a TFUI topic because GUIs interfere _again_ with that Flow.
For example, some errors might not bubble up from some GUI component
properly for us to see them in our test transcript...

--
  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/