On 10/31/07, Marc Esher <[EMAIL PROTECTED]> wrote:
> Sean, an you elaborate?
On what? The differences in the frameworks?
Here's the most important one that comes to mind:
Java doesn't have default parameters so in jUnit, the assert() methods
have: message, expected, actual. cfUnit follows that. Since the
message really isn't needed a lot of the time, you end up using named
parameters a lot in cfUnit.
cfcUnit takes a more idiomatic CF approach by acknowledging this and
placing message at the end, as an optional argument, so you just
assert(exp,act) instead.
cfUnit follows jUnit's method signatures and tries to deduce types
when you're asserting things. Java is strongly typed so it can figure
this out and cast things as necessary. cfUnit can't always figure it
out (because CF doesn't really have types).
cfcUnit acknowledges that CF is a dynamically typed language so it
provides assertEquals{Type}() methods so you, the programmer, can tell
the framework what types you expect.
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CFCDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cfcdev?hl=en
-~----------~----~----~----~------~----~------~--~---
