Hello,
I'm the CFUnit project manager. I just saw this topic on
CFUnit/CFCUnit, and figured I would put in my 2 cents.
David Ross Wrote:
> I've pondered why the creators of CFUnit didn't
> choose to just contribute to CFCUnit.
Well, I did originally search for a ColdFusion xUnit framework, and
first ran into the CFUnit built by Christian Cantrell for one of the
Macromedia DRKs. I then found a CFUnit project on sourceforge.net, but
it had been inactive since 2001. So needing a unit testing framework
for my team at work, I decided to submit to the sourceforge team for
ownership of the project. I then took JUnit almost line for line and
converted it into CFML, and revived the dead project.
Of course I did find CFCUnit shortly after taking over the CFUnit
project (a few days in fact), but did not think there was too much
overlap for a few reasons:
1. CFCUnit seemed to be CFC specific
2. The project looked rather inactive
3. It looked like it was Mach-ii specific
Of course, as mentioned earlier in this thread, the last few points
are not quite true.
However, I also personally feel that having more then one unit testing
option is a good thing (not sure Paul agrees with me on that :o) ). I
think frameworks having multiple options (Fusebox, Mach-ii,
Model-glue, Plum, onTap, Tartan, ...) has helped strengthen the
frameworks-community. In the same way I think a few different unit
testing options help strengthen the xUnit w/CF community (In fact I
think this thread itself is proof of that :o) ).
I think TDD is something often overlooked in the CF community and, if
followed, could have a huge impact in the average CF developer's
productivity. So, I think Angus Johnson is right-on with his comments,
unit testing your code is the important part, regardless of what you
use to do it. If all the CFUnit project does is grows awareness for
TDD for ColdFusion developers, then I am happy.
Oh, one last thing...
> (Q) It doesn't deal with NON-CFCs does it?
Let me just help the folks using CFCUnit out here. CFUnit does have a
few special methods for testing template (*.cfm) and module outputs,
but it's really not that hard for you to do too. I believe something
along these lines should work...
<cfsavecontent variable="myOutput">
<cfinclude template="/myfolder/mytemplate.cfm">
</cfsavecontent>
<cfset assertTrue( YesNoFormat(myOutput CONTAINS "Hello World!") )>
(Note: I just write this freehand, so it's just an example)
All the methods in CFUnit do is allow you to do this more easily, and
provides a few extra features (for an explanation of those methods:
http://cfunit.sourceforge.net/help-template.php)
Thanks,
Rob Blackburn
http://www.rbdev.net
http://cfunit.sourceforge.net
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
