the site was down for a good week or so there.. my domain name had expired and i decided to transfer to godaddy who is having a pretty sweet special right now ($7 to transfer your domain and get a free year out of it…). since i was going to have to update my dns again anyway, i figured i’d also switch over to rimuhosting’s fine dns management tools as opposed to zoneedit, which has some restrictions.

a lot of wild and crazy things have happened since my last posting.. namely the fact that we released jboss eclipse ide 1.5. this release represents the really hard work of about a year on behalf the entire ide team. i can’t tell you how excited.. and relieved i am that this release is finally out there. what’s more, it seems that santa has chosen to give me a late christmas present, as i just found out today that the total number of jboss eclipse ide downloads has surpassed the 1 million mark. quite an astonishing number, and i can’t wait to go for 2! we’ve got a lot of really exciting things planned for the 2.0…

with that out of the way, now i can finally get around to updating my open source software page, and posting my new cxxtest fork that i’ve been working on in my (oh so very little) spare time, aptly named Mock1. it seems the original author of cxxtest has all but disappeared from existance, leaving me to toy with it as i will. i got started by writing an eclipse plugin (naturally) that extends eclipse’s excellent cdt, and tries to mimick the junit functionality found in jdt. of course, none of this would have been possible without some way to transfer test information back and forth between the test framework and eclipse, so i implemented cxxtest’s TestListener interface that prints out a very simple xml stream. the plugin basically expects your c++ unit test application to use the xmlprinter, otherwise of course it won’t work. here’s a list of current functionality for the eclipse plugin:
- A very JUnit-esque view complete with total suite progress, failure list, overall test view, statistical information, error message, and a quick re-run latest test button.
- A cxxtest application launcher. This is basically a copy of the cdt application launcher, but hooks into the xml printed by the process
What I’d like to see happen for Mock1:
- Refactor everything to my cool name Mock1
- port cxxtestgen.pl/py to java for automated generation in Eclipse
- write a JNI test listener for native speed on win32/linux
- add the ability to run single and/or groups of tests in the framework (this will be nice to only run tests that have recently failed)

at any rate, if anyone is interested in helping out with the development of mock1 i could really use a main contributor who will stear the project more than i have time to. i am setting up a subversion repository with all of my code integrated with cxxtest sometime this weekend at which point anyone who shows me a single line of code will be given committer access ;).