On 10/31/05, Paul Kenney <[EMAIL PROTECTED]> wrote: > John, > > > > It sort of dropped off the map. Looks good, but looks like another > cryogenic > > project waiting for spring thaw. > > It really hasn't needed to be changed that much since I released it, so I > haven't. I'm still alive and as long as that is the case, cfcUnit will be > around, frozen or not.
That's what I wanted to hear :) I'd guess the low volume of email on the list/forums also speaks to low usage, which given the state of test-driven development in the CF world, is not a surprise... ;) > > You have to install and configure Machii. (Let's say that XML files aren't > a > > deal breaker here... heh) It still is a big jump to not have a complete > > solution. It makes sense that it needs to be written with some standard > and > > Machii is fine as the next for this type of task. It is ever frustrating > to > > have to learn a whole methodology to customize it. Yet, the plain fact is > > that if it was written another way the same thing would be true but for > > different people. > > I have addressed the dependency on MachII in two ways. The first is that I > have just bundled MachII into the installation of cfcUnit so that while it > may run on top of the framework, you don't have to worry about installing it > separately. The second solution was to write a non-MachII test runner > application that will run without any external dependencies. These are both > in CVS right now and need to be rolled into another release. All I had to do to get the testrunner running was define a /MachII mapping -- not a big deal in my mind. There was no XML config to do. And this is no different that having to install a testrunner gui in Java -- swing, eclipse plugin, whatever. Course in Java you can also just run it from the command line. > > I want my tester (this would apply to both) to be able to generate a web > > service, XML file or something so the testing could be entered into a > > project tracking system. > > This sounds like a feature request, and I'd be glad to hear more about it. > Why not pop onto the cfcUnit mailing list and pose it there or send me an > email. In the Java world, you check in the tests to your source control management system (eg Subversion) and then run the tests (using a testrunner) during each build (e.g. using Ant). Or you run the tests in your IDE directly. While the testrunner web app runs ok, you really need to be able to hook into the results so you can use them in the build process -- that may be in there already, but haven't dug too deeply yet. > > I believe the type of CF files supported is broader here. (Wonder if they > > will be supporting flash remoting .as files and such???) Hard to tell from the site. And the code for CFUnit seems to do far less -- I'm trying both for some CFCs (basically some function libraries) and will post a bit more about my experience. I *would* agree that it seems silly to have two competing project -- CFUnit *seems* to add the focus on non-CFC testing. CFCUnit *seems* to be more comprehensive for CFCs. While there's not a lot of motion on either -- would it be possible for the two leads to have a conclave and figure out how to best leverage both tools into a single platform? -- John Paul Ashenfelter CTO/Transitionpoint (blog) http://www.ashenfelter.com (email) [EMAIL PROTECTED] ---------------------------------------------------------- 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]
