www.protonarts.com--15% discounts during MXDU (today and tomorrow). Back to the issue of debugging: I'm ashamed that nobody has mentioned unit testing yet! Bad Fuseboxers, bad!! ;)
Unit testing is one of the hallmarks of Fusebox development. You first test each fuse with a test harness written according to its Fusedoc. This helps you debug the individual fuses, and makes sure they do what you expect them to do. THEN you can start running the integrated application and testing each fuseaction to make sure you haven't left anything out (unlikely if your Fusedocs are accurate). Oh, but writing those test harnesses is a pain, you say. That's why I wrote the Harness tool--it auto-generates a test harness for each fuse, according to the Fusedoc. Harness2 works with the current XML- based Fusedoc standard. You can download it from the Grok's Goodies section of www.GrokFusebox.com - Jeff On 17 Feb 2005 at 14:45, Andy Mcshane wrote: > Ok, thanks. Definately time to purchase a book. Can't yet find the Fusebox > 4.1 version on Amazon UK yet, don't really want to have to order from America! > > ________________________________ > > From: Michael T. Tangorre [mailto:[EMAIL PROTECTED] > Sent: Thu 17/02/2005 13:49 > To: Fusebox > Subject: RE: Newbie on Fusebox4.1 > > > > > From: Andy Mcshane [mailto:[EMAIL PROTECTED] > > Ok, I am really starting to get into this now but I have hit > > my first small issue so to try and save some time I thought I > > would ask the question. What is the best way/method for > > debugging fusebox applications? > > I would make sure I have a site wide error handler in place as well as a > couple cferror tags in the application.cfm file. I go with a much more > robust error/exception handling structure than this, but this is a good > start while developing. > > > Also, where would be the best source for me to find a list of > > the syntax/condition statements that I am allowed to use > > within my circuits.xml.cfm files, such as cfif, cfcase, etc, > > I have used the > > <if>...<true>...</true>...<false>...</false></if> command in > > one of my circuits and I would like to know the extent and > > limitations to the commands and syntax that can be used. > > I would have to refer you to Jeff Peter's books, or Techspedition's FB4 book > for a definite list and explanation (especially given that FB4.1 has more to > offer... looping, etc). > > This might also help you... > > http://www.techspedition.com/samples/DiscoveringFusebox4_XML.pdf > > Mike > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Purchase Captivate from House of Fusion, a Macromedia Authorized Affiliate and support the CF community. http://www.houseoffusion.com/banners/view.cfm?bannerid=52 Message: http://www.houseoffusion.com/lists.cfm/link=i:12:6633 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/12 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:12 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.12 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
