MXUnit

I setup MXUnit and the mxunit eclipse plugins on my local development environment. Tried it out on a couple of CFCs I had built for a project at work. I went through 3 round of tests on one of the CFCs and "walla"!! I found an error. I am sold on testing and MXUnit now. It is really cool to be able to just run these test, each and every time I modify the CFC.

A side note that may or may not effect very many people is a compatibility issue with the software I have installed. My employer decided to use Altiris to manage the migration of Lotus Notes to Outlook and office 2007. Altiris has issues with Eclipse, CFEclipse, Fusebox, MXUnit, CodeCop, etc... Certain XML file parsing will cause our systems to blue screen. The BSOD is usually when you browse the sites that parse certain XML files. Our company is actively troubleshooting this issue, no resolution yet. Fusebox needed a couple of XML files modified. CodeCop has not been fixed yet, BSOD every time.

MXUnit also caused a BSOD when browsing the MXUnit directory. With some help from Adam Haskell at work, there were two XML files found to cause BSOD (mxunit\framework\mxunit-config.xml and mxunit\doc\api\config\config.xml). All we needed to do to stop the BSOD was to remove the comments out of the XML files. This is probably only a bandaid so hopefully we will find the real solution to make Altiris play nice with our setup.

TODO in CFEclipse

Can't say how much I like the TODO comment feature in CFEclipse. See this article for more info. All you have to do is add "TODO" in a comment and it will appear in your tasks list.


inside scripts .... // TODO: Do this later

No excuse for forgetting stuff now .... unless you forget to use TODO!!