In the spirit of consistency, we’ve returned for another week of ColdFusion chat and Micky Dionisio is back in the fold and armed with knowledge. Before jumping in to Unit Testing in ColdFusion, we chat a bit about a blog post regarding ColdFusion Builder and share our thoughts on some ColdFusion Meetup presentations, first on ColdFusion Builder and next on BlazeDS with ColdFusion.
Just moments before we began recording, Micky opted to take the lead on the discussion on Unit Testing and instantly began to dive into the details with no hesitation. Unit Testing is a passionate subject for Micky which is evident in his coverage as well as his everyday usage of unit testing in his development work. We encourage your feedback and questions on Unit Testing and are eager to bring you more in the weeks to come. To get started, check out CFCUnit, CFUnit and of course MXUnit and experience the joy of the green bar!
We’ll chat with you again soon!
Listen Now!
Direct Download!
Download It!
Loading ...
#1 by Greg Franklin on April 2, 2010 - 10:25 am
Quote
Hey guys,
Great episode!
I recently created a facebook group called “Adobe Coldfusion Builder Should be Free!” if you’re interested in joining.
http://www.facebook.com/#!/group.php?gid=113188632029161
#2 by Brian Carr on April 2, 2010 - 10:29 am
Quote
Consider me a fan Greg! Sadly, I do not have a facebook account in order to make it official – but I most certainly support the cause.
#3 by Micky Dionisio on April 2, 2010 - 10:34 am
Quote
brian….. *hangs head i shame*
#4 by kripz on April 2, 2010 - 9:45 pm
Quote
Thanks. Very informative podcast!
#5 by Tony Garcia on April 5, 2010 - 8:45 pm
Quote
Hey Guys. Another great show. It’s nudged me back to looking into unit testing again.
I had a comment on the discussion you guys had about ColdFusion Builder. I noticed that there seemed to be some consternation about the fact that in order to use CFBuilder extensions, you had to buy a license for CFBuilder. I actually look at extensions as one of the features that justifies having to pay for a license. Of course one could, as you pointed out, just develop regular Eclipse plugins for free. But for those of us who aren’t java developers (and don’t plan on becoming one) the ability to add functionality to the IDE in a language we know (CFML) opens up all kinds of possibilities.
Also, this isn’t really anything new for Adobe products. Keep in mind that it’s been possible to develop Dreamweaver extensions and Photoshop plugins for years.