Ok guy's, I like the sound of the harness tool and it seems to be just the thing I could use but before I get too excited, I spotted the word 'Fusedoc'. Now, I noticed whilst I was doing my reasearch the odd mention of Fusedocs but did not pay too much attention at the time, so you guess what's coming now can't you? What exactly are Fusedocs, why have them, how do you create them and how do you use them? I can't remember exactly I saw these mentioned but I do not recall seeing any tutorials. ________________________________
From: Michael T. Tangorre [mailto:[EMAIL PROTECTED] Sent: Thu 17/02/2005 15:53 To: Fusebox Subject: RE: Newbie on Fusebox4.1 > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > 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, Good call. :-) However, I am still trying to get myself to spend enough time on writing the Fusedocs to begin with, let alone unit testing. I was reading in Eben Hewitt's Java for Cfers book last night about how a lot of Java devleopers will put a main method in their class files so they can "unit test" them without running into all the nitty gritty compile error nightmares when everything gets throwin into the mix. This got me thinking about our FB design and coding tasks.... maybe all fuses should have a unitTest() method or routine that is accessible when the mode is development. If this became a standard, wouldn't it have a huge benefit on the application and those who have to maintain it? Not sure where I am going with all this, just a quick thought that hopped into my head while reading up on some Java. Mike ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:12:6635 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
