Unit testing Fusebox 3/4 applications

A recent conversation prompted me to post this. I'm still quite suprised that people who are still in the procedural world (i.e. not using mach-ii etc.) are not making full use of cfcs. Let's not forget that they can still be used in procedural apps. Even if you are using fusebox 3 - at the bear minimum I would recommend putting the functionality which is encapsulated in act_ files or fbx_settings files into cfcs. If you're using fusebox 4 you can use the invoke tag to call CFCs directly. Why? well 2 reasons really, the first (and in my mind the most important) is that it allows you to unit test the core business logic of your application using a unit test framework such as CFCunit. The second obvious reason is it allows you in the future to easily move to another framework. I have come across a lot of Fb3 applications which make minimal use of cfcs - in my mind the ability to unit test alone is a strong argument for moving a lot of your logic in fusebox applications into cfcs.

links: digg this    del.icio.us    technorati    reddit